Running slow to not responding

[Mavors]

Hello all!

I am currently working on an application which has over 100 reports, 50 forms, and queries everywhere. The problem is that it is still growing and while I have seperated the data from the forms and reports it still gives me problems.

It is now to a point that I need to import to a blank database to be able to even edit the design of a past report or form. The compact and repair just stops helping and this seems to be the only way I can get my access back. At first this was a viable option as I only had to import to a new (blank) database at the end of every day...np, but now I am doing it on average of 3 times a day. It takes about 10 min to do an import so far, but with more to be added I am worried about this becoming a big problem which it seems to be.

Does anyone know of a reason why this may be occuring? I figure it is due to the size of the application and that it has to compile so much, but I am not really sure. Oh and once it reaches a state where you can't design you also can no longer run the forms either. It isn't till after you import to a blank that all seems right again. Any aid in this matter would be greatly apprieciated.

Thank you for your time,
Mavors

 

[tedsmith]

Hi, what language are you using, I have done jobs that big in Accesss version 1 and Access97 with about 12,000 records, 120 reports and about 50 forms with 40 fields. The file is about 40mb and it is just as fast to edit forms and reports as if it only had one form. Also it takes less than a second to find a record from a field that has been indexed.
There are buffers that can be varied in the MSAccess.ini file but it depends on the version of access. There is a read me on it somewhere.
I had problems having more than 50 fields in a query, using the dataenvironment, in a visual basic front end for Access, so I find code recordsets/dynasets are much easier to handle in the end
Ted

 

[Mavors]

Thank you tedsmith for the reply, but I think we figured it out.

I started checking out a lot of the defaults and settings within my access to see if I had a setting causing the very slow progress. I found it in the Options under the General tab. There is a check box for the Track_Name AutoCorrect Info setting. Once I unchecked all that autocorrecting it is amazing how much better access can handle the size of my project. So if any of you out there are getting some major slow downs under Access 2000 check it out. I believe it is an issue only now due to the fact that all the VBA code in the background must be saved after every change.

Thanx again,
Mavors