Modifications are slow

  • Thread starter Thread starter RLN
  • Start date Start date
R

RLN

Re: Access 2003
The FE is on the local drive.
The BE are two .mdb's in the same folder on a file server.
One BE .mdb has a History table with about 450k rows and is about 100 MB.
The other BE .mdb has about 1000 rows tops in any one table and is about 4MB.

Right now there are 2 concurrent users logged into the application daily.

When I am editing forms, etc. Access is really, really slow!

Example: I copy the FE .mdb to my local drive.
When I'm in Form design: I click a label control for example to change its
size. The time between actually selecting the object and the time it takes
for the cursor to change to "resize" or to type something different in the
control is about 20-25 seconds.
When I am in the VBA IDE, it takes forever to save my code modules then
compile them.

To effectively test the changes that are fixing a problem the user reported,
I would like to test the changes with the BE .mdbs on the server.

Are there any other ways around this other than copying the BE .mdb's to my
local drive? I really don't like to have to do that, because for every test,
I'll need to Un-Link and re-link all of my tables to point to my local BE
..mdbs instead of the ones on the server.

Suggestions if this were your situation?... thanks.
 
I never, ever, test using live production data.
Taking the time to relink when moving a new fe version to production is
nothing compared to the impact of corrupting production data.
 
Taking the time to relink when moving a new fe version to production is
nothing compared to the impact of corrupting production data. <<

Yes, this is wise counsel and you are very correct here. Thank you
 
Back
Top