Microsoft KB Archive/181833

{|
 * width="100%"|

-

The information in this article applies to:


 * Microsoft Data Access Components version 1.5

-

SYMPTOMS
When renaming an existing data source name (DSN), the Microsoft Desktop ODBC drivers allow you to overwrite an existing DSN without any warning. This occurs with the Microsoft Desktop ODBC drivers that ship with all versions of Microsoft Data Access Components (MDAC) version 1.5.

STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

Steps to Reproduce Expected Behavior
 Open Control Panel and open the ODBC Administrator. Create a User DSN going to a dBase source, and name it MyDSN.  Create a second User DSN going to a Paradox source and name it MyDSN.

This generates an expected error:

The datasource named "MyDSN" already exists. Replace it with this definition?



Steps to Reproduce Behavior

 * 1) Open Control Panel and open the ODBC Administrator.
 * 2) Create a User DSN going to a dBase source and name it MyDSN.
 * 3) Create a User DSN going to a Paradox source and name it MySecondDSN.
 * 4) Highlight MySecondDSN, select "Configure..." and change the name to MyDSN.

The change is accepted, no warning dialog box is displayed and one of the DSNs has been removed. Keywords         : mdac15Bug Version          : WINDOWS:1.5 Platform         : WINDOWS Issue type       : kbbug
 * }