Splitting - slow running

[Guest]

Hi.

I have read quite a bit about splitting an mdb and have now tried it on a
copy. I've produced a tables only Back End and put it on the server and
created a Front End (Forms Queries etc) that I've put on a local drive of a
PC. I've then linked them.

The mdb seems to be running just as slowly as before and I remember reading
about creating an invisible bound form that stays open and this improves
speed. Could anyone elaborate on how to do that please? In my case I have a
Tab Form that loads when the database opens and this acts as the Switchboard.
The Tabs show forms and subforms. Is it therefore not already the case that I
have forms that stay open? Or do the forms open and close when I move from
one Tab to the other?

Any help would be appreciated.

Cheers, JohnB

 

[Allen Browne]

John, take some time to work through the issues Tony Toews lists in the
Access Performance FAQ at:
http://www.granite.ab.ca/access/performancefaq.htm

It answers most of your questions, and others you have not asked yet.

BTW, the split database will not perform faster than an unsplit one, but you
will avoid other problems.

 

[Guest]

Thanks Allen.

I'll have a look at that.

I'm sure I read at least one source suggesting that one of the benefits of
splitting was faster running. Your own advice
(http://www.allenbrowne.com/ser-01.html) says "Loading the entire application
(forms, controls, code, etc) across the network increases traffic making your
interface slower." So I assumed you meant that Access would run slower -
perhaps you meant it makes the general interface slower for everyone,
irrespective of the application they are using.

Anyway, I can hear a strange grating noise - like the sound of a can
containing worms being slowly opened, so I'll leave it there.

Thanks again, JohnB