Thanks, I'll try the late binding with the subforms next weekend when I have some time to "tinker", and see if it helps.

And I'll try splitting a copy again and see what happens. (Toward the end of testing before we started populating is when I split it and found the lag and so we just didn't split it. The lag occurred whether the FE was on my local machine or in the same Share folder on the server as the BE. The server lives in the other end of our building...)

Thank you,
Loralee

Thanks for all your replies etc. I've got plenty to be going on with. However, I've another problem, I converted all my queries to pass-through. and now I'm having trouble with ODBC. Im sure I'll hit upon the cause of the problem eventually, but I thought whilst I'm scratching my head I'd ask if there is something specific I'm looking for. Everytime I know try to access a table or run a form etc, it pops up asking me to select an ODBC connection. I've set one up to my SQL Server but it doesn't work. I'm not sure what I'm doing wrong!

Loralee, I've heard that the FE/BE situation performs better if you stick to the 8.3 DOS naming convention for files. Apparently Jet has to convert Long File names to 8.3 to perform the work. And it calls Windows routines over and over to do that.

Rob, mmcdonal will have the most appropriate answer. But I think that when you open your database, sometime during startup you need to create an ADO connection that stays open until your database is closed. Wish I could help more.

I use file names for my front ends like this:

"ABC MedSurv Administration Rev 03.mdb"

And I don't have any problems opening them. I think the issue is that there is just a shortcut to the front end file, and all users are opening the same front end file. This will kill your app. Have them each save their own copy of the front end file to their desktops.

The ODBC issue sounds like you did not create a System DSN to connect to your SQL server. Did you do this? If so, then you may still have to log in to the server if you are not using Windows authentication. Perhaps your SQL administrator can help you on this one.

mmcdonal

This is really confusing me, When I set my queries to be pass-through, I repeatedly get an DSN selection box appear. I have an ODBC link to my SQL server set up, using trusted connections, and the test button works fine. I have set up my linked tables to use the correct DSN (these work ok when the queries are local). I'm clearly missing something simple, but I can't for the life of me work out where it is!