Front-end/Back-end Performance Help

[Steve Schacher]

I am trying to split a database to try to enhance performance
over a network. I read prior posts and some of the linked FAQ's and
tips, but I'm probably still not doing something right.

I have a database with only a few hundred records in each table (many
related tables). The thing is, I have several users in California and
several users in Manila that I'm trying to deploy the database app to.
The database is in California; Manila users access it over the company
network. Originally, they ran from the MDB in California.

I tried splitting into a front-end and back-end MDB. The back-end is
on the network, the front-end I emailed to a user in Manila and he
copied it onto his desktop.

Even when a user clicks on a combo box that is populated from a table
with only a dozen records, my performance hangs. I'm not sure what I'm
not doing right, since I built the system with mostly wizards, with
tweaked code where needed. The tables I built by hand. My expertise is
in SQL, not VB (or VBA), so I don't know if there is any housekeeping
code that I need.

Any suggestions?

Steve Schacher

 

[Kevin3NF]

Your performance over a WAN is going to bite.

There is an outstanding article here:
http://www.attcanada.net/~kallal.msn/Wan/Wans.html

Your best alternative is either a Terminal Server setup, or taking it to a
web based app.

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm