View Single Post
  #4  
Old April 8th, 2010, 10:29 PM posted to microsoft.public.access.tablesdbdesign
szag via AccessMonster.com
external usenet poster
 
Posts: 99
Default Splitting database - terrible performance

Sounds like great advice. Thanks!

Dorian wrote:
What I do is to have a copy of the back-end on my local drive.
When I make updates I link to this local copy.
When deploying the changes, I just redo the links to point to the production
database.
-- Dorian
"Give someone a fish and they eat for a day; teach someone to fish and they
eat for a lifetime".

I split my database recently and now I am experience terrible performance
when designing my forms. It can take 10 seconds just to select a field and
delete it. Or when I go into the design view of a form it may take a minute.
I realize that it might add a little time because of splitting but something
is obviously wrong when I have to sit and wait every time I click the mouse.
Help!!


--
Message posted via http://www.accessmonster.com