© 1998 Microsoft Corporation. All rights reserved.
Other product and company names herein may be the trademarks of their respective owners.
Microsoft Visual Database Tools Readme includes updated information for the documentation provided with Microsoftâ Visual Studioä -- Development System for Windows® and the Internet. The information in this document is more up-to-date than the information in the Help system. Many of the issues outlined in this document will be corrected in upcoming releases.
This release is provided for evaluation purposes only. It contains pre-release code, documentation and specifications, and is not at the level of performance and compatibility of the final product offering.
This release is confidential and proprietary to Microsoft and its suppliers. Do not disclose or provide copies of this product or any information relating to it to any other party, or use it for any other purpose than as provided in the End User License Agreement without the prior written consent of Microsoft.
Contents - Click any of the items below
To find out about the features that are new to this version of Visual Database Tools, look in the Help file's table of contents for "What's New in Visual Database Tools," located in the Reference section of the Visual Studio Documentation node.
The following issues are known in this March pre-release of Visual Database Tools. For product-specific issues, refer to the readme for the appropriate product.
The Visual Database Tools are only certified against the latest Microsoft ODBC and OLE DB drivers. If you are encountering unexpected behavior, verify that you are using the correct drivers.
Expanding stored prcedures that return multiple result sets is not supported in this pre-release version. If you expand a stored procedure that returns multiple result sets, the Data View returns the error "[Microsoft][ODBC SQL Server Driver][SQL Server] Procedure 'procedurename' has no parameters and arguments were supplied." As a result, you won't be able to inspect the stored procedure parameters, output columns, or return value. You will need to inspect these attributes by opening the stored procedure in an editor.
When building queries against Oracle tables, you will not see column information in the Diagram pane if the user name you logged in with doesn't match the case of the schema name. When logging in to the Oracle server, make sure your user name matches the case of the schema name.
If you execute an action query that violates a constraint at the server, the resulting error message says "Unknown Error". If you encounter this error, close the message and then check the table constraints and adjust your query to aviod violating them.
If you're working concurrently with Visual Basic and the Visual Database Tools, be sure to close the Visual Database Tools before you close Visual Basic. If you do not close the Visual Database Tools first, you will be prompted to save your changes. However, cancelling the prompt will cause errors and you might lose data.
When opening a table using the Data View, you are actually opening the Query Designer with a "SELECT * FROM table" command. To open the Diagram, Grid, and SQL Panes in Visual Basic, from the View menu click Show Panes. This allows you to choose which panes you want to open and close.