Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It is hard to reply because the origin of the problem can be multiple. Since the two clients has not the same OS configuration, we cannot exclude that the problem comes from a difference of configuration between the two OS.</p> <p>First you can discern if the connexion is slow because of the PC, Access or your DB :</p> <p><strong>Test : direct connection</strong></p> <p>You can try the direct connexion to SQL server using a direct connexion instead of linked tables. For this, you can create a new Access Project connected to your SQL Server. An Access Project is a type of Access database which directly connect to an SQL Server, without linked table. It uses a native client. You can view tables of your SQL Server database directely in Access, and you can edit them. The extension of an Access Project is not MDB but ADP. Access Projects are hidden in Access 2010 but well supported. </p> <p>To create an Access Project: go to menu File -> New, then click of the file icon, and then choose "Save as type" : "Microsoft Access Project (*.adp)". </p> <p>When the ADP is created, it should ask you to enter the parameter for an existing SQL Server database. Enter your parameters.</p> <p>Then go to the table panel, and try to browse some table and check if it is slow or fast.</p> <p>If it is slow => then the problem may comes from your PC or the connexion. You can try with another software for testing the direct connection of you have one that can connect to SQL Server.</p> <p>If it is fast => then the slowness comes from the ACCDB or the ODBC link.</p> <p><strong>Also check :</strong></p> <ul> <li>Ms Access is up to date with last version and Ms Office patches</li> <li>your ODBC system and "ODBC driver to SQL Server" are up to date (take to last version of <a href="http://msdn.microsoft.com/en-us/data/aa937730" rel="nofollow">MDAC</a>)</li> <li>Your Windows 7 and Ms Access and ODBC versions have the same bits range (32-bits or 64-bits)</li> <li>Your DSN string for the ODBC connexion to SQL Server is normalized</li> <li>If your DSN is a system DSN, then recreate a new one as a user DSN and try.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload