I have a Access2003 program that consists of a front end and a back end. The data is contained in the backend. I have a table that contains, and will always contain between 12 to 15 thousand records. Sometimes those records need to be edited or deleted and new ones added. I have noticed that after I start the code to edit them the speed of the code slows to a crawl and the database swells incrediable. For example the backend starts at about 15 megabytes and after I edit some 5 thousand records the backend size is 180 megabytes. It shrinks back down after I compact it.
Is the code I am using faulty such that it would slow to a snails pace after running awhile and increase the database size so much or is it Access itself. Is there a way to privent this from happening? If need be I will include the code but I wanted to save readers the time if it is fact not the code.
Thanks.
Is the code I am using faulty such that it would slow to a snails pace after running awhile and increase the database size so much or is it Access itself. Is there a way to privent this from happening? If need be I will include the code but I wanted to save readers the time if it is fact not the code.
Thanks.