Possible issue with SQL connection String

MaliciousMike

Registered User.
Local time
Today, 14:25
Joined
May 24, 2006
Messages
118
Good afternoon.

We're running an Access front end using SQL Server 2005.

We have 2 seperate offices which use this application. The 2 office are linked wirelessly.

One office (our call centre) uses it constantly, and this office has the SQL server and everyone is hard wired into the network.
The other office (the one I work in) uses the application mainly for developing more forms/queries/reports etc. We are also hard wired, but obviously have that wireless "jump" between the offices.

As the developer, I expected it to run a lot slower because of the travelling it need to do to the other office, however it seems to be working a LOT faster over here and it's causing more and more issues.
The SQL connection string used to reference my computer name (because I wasn't very knowledgable with that sort of thing at the time), however now it has been removed but it doesn't seem to make much of a difference!

The biggest table holds nearly 100,000 records and is growing a lot.
Here is it's connection string:

Code:
ODBC;DRIVER=SQL Server;SERVER=SQLPC\SQLEXPRESS;APP=Microsoft Office 2003;WSID=;DATABASE=Inky2SQL;LANGUAGE=us_english;Network=DBMSSOCN;Trusted_Connection=Yes;TABLE=dbo.tblAnswers

Can anyone think of any reason why it may be faster in an office which is not directly hard wired to the server?

Thanks for any help you can give. Getting this speed issue sorted would be a HUGE weight of my shoulders.
 
Last edited:
Can no one help with this?

Apologies for the bump but I'm lost!

Can anyone point me in a direction which would help?
 

Users who are viewing this thread

Back
Top Bottom