Why is split db so slow?

Skeletal

Registered User.
Local time
Today, 17:41
Joined
Mar 10, 2005
Messages
33
Hi all

I have an Access 2003 db that works extremely well as a stand-alone application but I am keen to “split” it so that many users can operate it together.

Accordingly I did the split and placed the tables on our server, and tried running the front end locally.

Much to my horror, it takes about a minute to open, and many seconds to do anything after a button press etc.

I have been testing it on my wireless home network and the same thing happens, except now I can monitor network activity from the “network working” light.

What I see baffles me and would welcome comments, in particular, what I can do to speed it up by a factor of 100!

1. It takes forms about 50 seconds to open; however, this is due to about 40 seconds of network activity BEFORE the form’s load event fires!
2. In DESIGN mode, any minor change to a control for example, results in about 40 seconds network activity.
3. All queries upon which forms are based take well under a second to run over the network.
4. Making an mde file has no effect.

I thought the idea of splitting was to keep the forms/queries/code etc, local to a machine so I don’t understand what all the network activity is about, particularly in design mode. Also, given the actual queries are so fast, just what is Access doing??

Any comments please?

Skeletal
 
May be on to something: I use long file names, cutting them to 8 digits seems to have speeded things up.

I need to experiment more...too late now but will post with more info over the next day or two...it could help others in the future.

Skeletal
 

Users who are viewing this thread

Back
Top Bottom