Have you tried to Compact & Repair the database?

Yes. sorry i forgot to mention. I deleted links to the db backend and ran compact and repair in the backend and all 5 front ends.

Try Decompile as well, maybe finds something. Otherwise where is your back end located? On a LAN/WAN server or SQL server or I hope not something like Google Drive? That could affect your speed as well.

Other question would be do you have like a ton of global constants or temp vars for some reason just clogging you up? (Like a ridiculous amount)

Also a 200MB front end seems pretty big, do you have a bunch of images or something stored in it?

Thanks Adam. the back end is on my server. Should i compile the back end and all front ends and should i break the link tables to complie? or should i compile my front end and redistribute to the other work stations?

I use Richard's method of images where images are stored in a file with a link in the form. I probably have a bundle of querries that i could delete - would that help?



Thanks,

John

If you want to be super sure, you shouldn't need to de-link your tables, run decompile and compact/repair on your front end, and on your back end. Then redistribute.

Do you have a solid connection to your server? Not latency issues getting to it? Try to ping it from command line and see if you have packet loss or delays.

Hi John, what exactly is slow?  Also, you said your BE is 50MB and FE 200MB?  Should it be the reverse?  BEs are usually much bigger than FEs after compact.  If your BE is 200 MB and FE is 50 MB, that is actually normal.

My IT guy checked - no latency issues.

Opening a form based on a query seems to take longer than it use to. maybe only a few seconds, but longer...

BE is 50,568 and FE is 182,696. I would think BEs are smaller because they ar just tables, while FEs have all of the querries, forms and reports. I have a lot of calculations, drop down lists and stuff like that...

Yea, its the exact opposite. BE are bigger because they are all the data, and FE are just a shell to access that data in. Unless you have some embedded stuff (images/documents) they usually aren't that large.

If you've done the compact/repair and compile stuff. I would be inclined to think the next most likely thing would be a network issue with communicating. Perhaps take just one table/query out of your database and make a separate database with it, throw it on your server, and see if you're still experiencing delays.

Hi John, I would go into VBA debug mode while the problematic form is opening.  Set a break point in the VBA editor, at the first line of the Open event of that form, then open the form normally and run a line-by-line debug from there.  If a line is taking a long time to run, you may notice it.