Hi!
There is explanation somewhere in the HELP for Access or in MSDN library. Access even contains built-in tool to split database by such way. The reason I think is in the way Access works with forms and their content. Often queries through network might work slowly, indeed, when locally this makes no difference than often read of the same file.
>Hi Vlad,
>
>I did split the database in two, but I didn't install the application database locally. Because there were too many updates, I thought it'd be easier to leave the database on the network drive (since this is an internal application, I can put my updates there and don't need to go around copying files everywhere). Now I see there is a big difference if I put the application locally (just tested it). I wonder why I haven't thought of trying this.
>
>Still I wonder where this difference comes from. Having the application on the network, a form can take several minutes to load, now it's just a few seconds. Do you have an explanation for this? In the time it takes to load a form, I can copy the whole database 20 times from the server to my local drive. This seems ridiculous to me. Is there a logical explanation?
>
>Thanks for helping.
>
>Auke
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.