Unsplit Database?

[AJD10]

Hi,
After much thought and reading into this, I decided to split our MDB that sits on the network, which is horribly slow. Figured it'd make it faster to have forms load locally instead of trekking to the server, right?
Well, it's actually even slower since it has to go back to the server for every drop down. I've only tested it from my laptop and I'm absolutely frustrated - no need to get everyone else riled up.

Did I make a mistake in this? I feel like I should've kept it together. What do I do now?

 

[mpastore]

I think split was the way to go. You would still have to go back to the server even without a split because the ap is running on the local workstation and the data source is on the network.

You may want to look at loading some of the tables that are list sources to the front end database at start up. This will speed things up but may be an issue if the tables are very large or change often.

Mike

 

[scking]

A design consideration is which tables to keep in the client and which to place in the server. If the data in the tables used by the combo box do not change, as in a validation table, keep them in the client. If the data used by the combo box is a dynamic field which may be changed frequently or by different users then place it in the server.
-------------------------------------
scking@arinc.com
Try to resolve problems independently
Then seek help among peers or experts
But TEST recommended solutions
-------------------------------------

 

[AJD10]

That sounds like a good idea. I'll examine the tables and see what I can transfer over to the front end.

Thanks!