Question about database size

[ukdane]

I understand that the best way to create a database that keeps control of warehouse stock, is to have a table that lists all movements of stock, both in and out, and when it is required to know a total amount of stock, that the figures are calculated in a query. However, as the flow of new stock in, and sales orders out expands, won't this have an effect on both the database file size, and the speed at which query calculations can be made?
What is the best way around this?

[OBP]

Access queries are very fast and can handle a table of a Million Records in a about 10 seconds. It obviously slows down the more complicated that the processing gets.
Database size can be kept to a minimum by regular Compacting & repairing of the database.
As far as query calculations is concerned you can design the query to exclude old data that does not need to be considered. Also the design of the Tables and Relationships can help this process.
However sometimes it is actually quicker and easier to manipulate the data by storing some "Calculatable" values in the tables, so I don't take the "always calculate value on the fly" as written in stone.
If you want advice on the table structure post a screenshot of your Relationships.

One other thing you could consider is Archiving data over a year old in another table in the current dataabse or a separate database and link to it for year on Year analysis, as the rest of the time the data won't be used.