tom in houston
New member
- Local time
- Today, 00:18
- Joined
- Oct 25, 2012
- Messages
- 7
Hi:
I'm having trouble with linked tables.
Basic Setup - Access2010 connecting to a shared SQL SERVER 2005 (provided via databasemart). Access FE has linked tables to SQL Server tables. DSN-less connection using the following string:
strODBC = "ODBC;DRIVER=SQL Server;SERVER=" & strServer & ";DATABASE=" & strDatabase & ";UID=" & strUserName & ";PWD=" & strPassword
Initial routine is to drop the link and recreate it for the 6 or so tables. Most of the tables are pretty small - few doz records. Two tables are large, largest being 500K records. Next a dialog box comes up with one combo box on it with a link to a small "facility table" to allow the user to select the facility to work work (i.e., which subset of the records). Once done, the main form comes up with 3 or 4 records loaded including a subform that may have a few dozen records.
On my development box, the whole process is quite speedy - basically what you would expect in launching access on a good speced machine. However on the client's box performance is a real drag. Maybe 20 seconds to get to the dialog box form and just as long again to open the main form. They have a brand new computer, with all current updates running a fresh install of Access2010.
When the client's box was in my office connected to my network , performance was as good as on my development box. On their network - sucks...
Additional data point - if I open a complex query in SQL SERVER Management Studio and run it, the query actually returns results faster on the client box than on mine! I looked at rated upload and download speeds from our respective ISPs, and the client actually has a faster connection.
Finally, if I drop the linked tables and just run reports via pass thru queries (and set the facility in code), response speed is fine. It seems therefore its something to do with linked tables.
Any suggestions on what is going on? Or how to fix without getting rid of linked tables? If I have to get rid of liked tables, I've identified two alternatives for the forms - assigning an ADO recordset as the forms recordset or using pass thru queries as the forms recordset. ADO won't work since the subform is a continuous form. I'd like to avoid pass thru's since they don't give editable data.
Thanks
Tom
I'm having trouble with linked tables.
Basic Setup - Access2010 connecting to a shared SQL SERVER 2005 (provided via databasemart). Access FE has linked tables to SQL Server tables. DSN-less connection using the following string:
strODBC = "ODBC;DRIVER=SQL Server;SERVER=" & strServer & ";DATABASE=" & strDatabase & ";UID=" & strUserName & ";PWD=" & strPassword
Initial routine is to drop the link and recreate it for the 6 or so tables. Most of the tables are pretty small - few doz records. Two tables are large, largest being 500K records. Next a dialog box comes up with one combo box on it with a link to a small "facility table" to allow the user to select the facility to work work (i.e., which subset of the records). Once done, the main form comes up with 3 or 4 records loaded including a subform that may have a few dozen records.
On my development box, the whole process is quite speedy - basically what you would expect in launching access on a good speced machine. However on the client's box performance is a real drag. Maybe 20 seconds to get to the dialog box form and just as long again to open the main form. They have a brand new computer, with all current updates running a fresh install of Access2010.
When the client's box was in my office connected to my network , performance was as good as on my development box. On their network - sucks...
Additional data point - if I open a complex query in SQL SERVER Management Studio and run it, the query actually returns results faster on the client box than on mine! I looked at rated upload and download speeds from our respective ISPs, and the client actually has a faster connection.
Finally, if I drop the linked tables and just run reports via pass thru queries (and set the facility in code), response speed is fine. It seems therefore its something to do with linked tables.
Any suggestions on what is going on? Or how to fix without getting rid of linked tables? If I have to get rid of liked tables, I've identified two alternatives for the forms - assigning an ADO recordset as the forms recordset or using pass thru queries as the forms recordset. ADO won't work since the subform is a continuous form. I'd like to avoid pass thru's since they don't give editable data.
Thanks
Tom