Web Development

Ask something
Discussion Locked

Access Database Splitter

0 helpful
11 replies

by gregory51

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am having performance problems after splitting an Access database. The database is located on a file server both before and after splitting, but the speed to load forms degrades significantly after the split. There is no difference when the "frontend" is loaded on the local workstation. Any suggestions for improving performance?
[using Access 2000, Win 2000 Pro and Win 2000 Server]

11 replies

by sandymac

Are you sure this is not just a problem associated with a slow network? I have used a split database over the network without speed problems (both parts on the server). Have you repaired/compressed the databases? I presume you know about recent Access versions using 2 bytes where one would do - for compatibility with Japanese. (This can be turned off!

by gregory51

Thanks, but the speed over the network is fine before the split. The difference is considerable too. A form that loads in 1 second before the split takes over 30 seconds to load after the split. Since submitting the question, I tried doing a "manual" split, and the results were much better, although still not great.

by bob sellman

I've got many split Access databases and have not experienced problems, unless the network is slow.

I assume that your "back end" database contains only the tables and nothing else, while the front end contains everything else.

As mentioned, be sure to compact the front end and back end, which I assume you've already done.

How are your tables linked? There could be a problem with the speed of finding the server where the back end database is located (even if it's the same server wherethe front end is) because of router and other network related problems.

For example, as a test you could map a drive letter on the workstation to the location of the back end, then use that drive letter to link to your tables. If you see a definite difference then that might provide a solution.

Also, try loading the front end AND the back end on the local workstation to see what kind of speed you get with that setup, since that eliminates the network entirely.

by gregory51

Thanks. I tried all combinations of split/not split, local/server. My best interim solution was to do the split manually, rather than have the wizard do it. Speed is barely acceptable for regular use, but it remains terrible for designing forms and reports. Which is very strange since they are all on the local workstation.

by ananthap

It looks like it's a problem with re-organising data on the server. Is one of the "splits" on a slower device? Is one of the two splits hitting a bad disk spot?

Next alternative, split another database and verify. If the same thing occurs then simply re-install axs.

End of mail.

by gregory51

Thanks. (Actually the answer did help somewhat, but if I say "it helped me" then no more answers can be posted) I tried moving the back-end to another server, and I saw a very minor improvement in performance, but still not to an acceptable level.Most perplexing: Why does it take a long time to save a modified form which is stored on my local PC, not the server?

by pancras

Does switching autocorrect off helps??
I had a major performance boost on one project with this thing off

by gregory51

This material was very helpful, and the suggestion to turn off autocorrect was the key to my problem. It did give a very substantial improvement in performance. I suspected there was some little thing hiding in there, and I thank you for pointing meto it.

This discussion is closed to new replies.