January 8, 2009 at 9:28 am
OK, thanks for the conclusion. I am pleased its not my db and pretty confident its not the network - our web apps are working without any user complaints.
One last question if I can take a little more of your time please?
If I get my VBA sleeves rolled up what should I look to change in the application? I would guess from previous experience of maintaining similar solutions that there is a section of VBA that creates an ADO (or maybe DAO) connection and then executes a SQL script via that object. Will simply setting that to execute a stored procedure improve anything much or is it time to embrace a new method of connecting to the data?
many thanks
Jonathan
January 8, 2009 at 9:31 am
Something I hadn't thought of earlier, but you might check the ANSI settings on the connection string from Access. If you use the ANSI standard settings, performance should be fine, but deviating from the default can cause some performance issues.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply