Unanswered: Slow Connection with linked tables on server.
I have a split database on a server. With either the front-end run from the workstation on its hard drive or on the server, it takes about 15 or 20 seconds to get connected to the back-end tables and load. That's an incredibly long time. I've just installed the database there so there's no large amounts of data in the system. In fact, even when connecting to tables/queries from forms with NO data, it takes a long time. It seems, however, that once the connection is made the first time, it doesn't take as long to connect the next time during the same session.
I've checked to make sure it wasn't a super slow network by going into the back-end from a workstation and looking at the data. It loads at a reasonable speed. Can anyone help explain this situation and offer some potential solutions. I'd greatly appreciate it!
I test two computers, one has etrust (anti virus) installend on it, one donesn't has, the second one run faster. But i am not sure what the problem is. Hope somebody has experience on this problem. We are waiting.
Just idea but I am on you already thought of it, but compress your db can help. Sometimes on our network we have this problem when our users send many print file on the server.
idea reboot the server....
Well, if there was any data at all in the database I would consider this a possibility. But there's nothing in all the tables except one and they're all having the same problems. I could try rebooting the server, but I'm not sure that would help anything. . . .
Thanks, ghozy! This seems to be exactly what I need.
I have a question concerning this subject. I use a mixture of bound subforms and unbound forms. I use ADO to add records using the unbound forms. Is there any foreseeable problem using ADO on a server? Will it have to create a connection each time the "Save" button is pressed and then close it, only to repeat each time the Save button is pressed? Or will it use the same connection created and maintained in the method that's outlined in those links? I'm hoping it may use the active connection since I do use the
it should use active connection. the problem is if there is no active bound form open, access will close the connection for the sake of saving system resources. therefore one suggestion is always keep open a hidden form that bound to a dumy table in the BE database. as long as you keep this hidden form open, access will retain connection to BE. at least this is what I understand from articles.
there are other suggestions like keeping unchanging tables in FE instead of BE. probably like city names tables, zip code tables, color type tables, etc.