split database over network (front end-back end) runs very slow.

[Guest]

I have a database that I developed in one db and then split into one db that
contains all the tables, call the back-end db, it sits on a Server. I have
the front-end db it runs locally on each computer. The database is not that
big. It runs great when the front end and the back end are on the same
computer. But when the back-end is placed on the Server that where the
problem is. At home I run fast DSL (750 Mbps Plus) and at work 100T Ethernet.
These are some of my problem

When I use the LINK TABLE MANAGER to link front end db to the back-end db on
the file Server it can take 4 to 5 minutes to do the link.... this seems like
I have a problem

Over the Ethernet the performance is slowed, over the DSL the performance
can be so slow it unusable.

Could the problem be caused because in each database, the front-end and
back-end, I have the RELATIONSHIPs for each table, should this sit only on
the back-end database?

Thanks,
Brad

 

[Douglas J. Steele]

DSL is definitely not sufficiently fast for Access.

You might want to read what Albert Kallal has to say about using Access over
the WAN at http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

As to your question about relationships, they should only exist in the
back-end. They do nothing in the front-end.

 

[Gord]

Hi, Doug.

DSL is definitely not sufficiently fast for Access

As Albert suggests in his article, DSL is not fast enough for _Jet_,
However, I have an Access database that uses MySQL as the backend and
it works remarkably well over my DSL connection.


Gord