Search results

Not a bad thought... I use a 'version' table to compare server vs client and copy over a new interface if this changes so the same process would cover it. I guess I could do away with the initial linking process entirely. It was useful though, as I could make backend design changes without too...

The procedure has always run behind a splashscreen, so users know to wait. It only runs once on launch, so it's not the end of the world I suppose, but a shame this now takes so much longer.

This is happening in multiple places, different ADs with different clients and different servers (and different implementations). It seems to have been happening since update 2109 14430.20270 for Access. At this point it only seemed to affect compiled (accde) dbs. Any user with 2108 or earlier...

I'm using: strSQLConn = "ODBC;Driver={ODBC Driver 17 for SQL Server}; Server=MyServer; Database=MyDB;Trusted_Connection=Yes;" so SSO for authentication, but looks ok (and has worked for at least a decade bar some not recent tweaks for TLS) otherwise.

Using 2019 here, 2016 at a separate place with the same issue. ODBC v17. Actually, I think manually linking may have a delay too. It's very hard to tell. I've just run through the code and put a timestamp/tablename debug.print statement in, and every table consistently takes one second to link...

Great question. Just tried, and no. That's interesting. Continuing to step through and examine...

My apologies for the thread bump here. I've been using this method to link backend SQL tables on several DB applications for probably over 10 years now. Recently, every link seems to take about 3 or 4 seconds to establish. Is anyone else seeing the same? Not good when there are 100 tables! I'm...