PRB: UserId and Password Viewable in Database Container

Last reviewed: April 30, 1996
Article ID: Q130579
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, version 3.0

SYMPTOMS

The userid and password for an ODBC connection are stored in the database container (.DBC) and are visible to the user if a connection is created for the database. If previously created data sources are used in an ODBC view rather than an ODBC connection, the userid and password are not viewable in the .DBC.

CAUSE

When a view or connection is established in Visual FoxPro, you have the option of specifying the userid and password at that time. If you enter them, they are saved in the DBC, so they can be seen by using the DISPLAY DATABASE command or by using the DBC as a table.

RESOLUTION

To maintain security, do not specify the password when setting up the connection or view. Rely on ODBC to request it. Then the DBC will contain only the Datasource name.

When creating an executable file, you can explicitly include the DBC in the project. In this case, the user is not able to display the connection information. To make this modification, choose Include from the Project menu with the DBC selected in the project.

STATUS

This behavior is by design. The reasoning for this design is that if you want to save the password in the DBC, you probably want the convenience of never needing to type in a password.


Additional reference words: 3.00 VFoxWin kbfest encrypt
KBCategory: kbinterop kbprb
KBSubcategory: FxinteropOdbc


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: April 30, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.