There are several issues that can cause slow performance or problems loading data in inFlow On-Premise.
Your server computer should have 4GB RAM at minimum, though the more the better! You can check this in Start > Control Panel > System and Information > System. A high processor speed also helps. Please refer to our minimum requirements here.
If you’re under 4GB RAM, you’ll need to upgrade it as it will be too slow for inFlow to perform tasks like loading a list of your products, generating reports, etc.
When you use inFlow’s multi-user mode, it relies on your network connection to load the data on client computers. To determine if it’s your network that’s causing the issue, try loading an order on the server computer and see how long that takes, and compare it with loading the same order on a client computer.
It’s hard to gauge your network speed, but if you notice that your speed is slow, you may want to check with the person who set up your network.
inFlow isn’t designed to work with negative inventory — every time you update an item that has negative inventory, inFlow has to recalculate all of the transactions starting from that point it reached negative inventory. So if you’ve never added stock / adjusted stock to deal with the negative inventory, then it will do a lot of extra work for that calculation.
To check if you’ve got lots of negative inventory, go to Main Menu > Inventory > Current Stock and sort by Quantity. If you have any at negative inventory, count the physical quantity and update that in inFlow.
If you’ve been using inFlow for a really long time now and your database is growing too big, you might run into issues with performance.
You can check the size of your database files here:
Windows XP/Server 2003:
C:\Documents and Settings\All Users\Application Data\inFlow Inventory
Vista, Windows 7/Server 2008, Windows 8/ Windows 10:
Look for a file that says inFlow.mdf (or just inFlow). You should see its size next to it. (For reference, 1GB = 1024MB = 1,048,576 KB!)
You can expect to see some slowness around 4GB or so, depending on your hardware.
If your database is nearing 10GB, you will need to archive your database.