ACC1x: How MS Access Handles Logins to Attached SQL Tables

Last reviewed: August 6, 1997
Article ID: Q93145
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1

SUMMARY

How Microsoft Access handles a login to an attached SQL table depends on how the table was originally attached, and whether the login and password were saved with the table information. It may also depend on who attached the SQL table, what rights that person has to that table, what rights you have to that table, and where the tables are located (different servers, different databases, same database).

MORE INFORMATION

If the "Save login ID and password locally" option was enabled when a SQL table is attached, you will not be prompted for a login ID and password. Instead, you automatically receive the rights to each table that are appropriate for the login ID used when the table was attached.

If this option was not enabled, you are prompted for a login ID and password once for each unique data source, and you receive the rights to each table that are appropriate for the login ID that you use.

NOTE: A unique data source is composed of the unique combination of a SQL server and a database on that server.

So, if you attach multiple SQL tables and use different login IDs with different rights for each table, but do not enable the option to save the login and password information, the next time you access the tables, the login ID and password you supply for each data source will determine the authority you have to the tables from that data source.

REFERENCES

Microsoft Access "User's Guide," version 1.0, pages 60-62 and 66-68

Keywords          : OdbcOthr kbusage
Version           : 1.0 1.1
Platform          : WINDOWS
Hardware          : x86
Issue type        : kbinfo


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: August 6, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.