| 30158 | When you are using the Shape Provider, it is not possible to cancel an asynchronous operation. The data Shape Provider does not pass the Cancel on to the underlying provider. Microsoft has confirmed that this is a bug in the Microsoft products... |
| 30159 | When you use ActiveX Data Objects (ADO) and set the CursorLocation property for Connection or Recordset to adUseClient , and specify asynchronous fetching with adAsyncFetch and adAsyncFetchNonBlocking for the execution options of the Execute or... |
| 30160 | The ODBC Driver Manager does not convert Unicode parameter data to ANSI during a call to the ODBC API SQLBindParameter , even when the ODBC driver involved is ANSI. If the ANSI driver saves this parameter data (that is in Unicode format) into its... |
| 30161 | Installation requirements for the MDAC update that is described in Microsoft Security Bulletin MS06-014 |
| 30162 | MS06-014: Vulnerability in Microsoft Data Access Components (MDAC) function could allow code execution |
| 30163 | Error messages that you may receive when you download a Microsoft Data Access Components software update package from Microsoft Update or from Microsoft Windows Update |
| 30164 | You are prompted to send an error report to Microsoft when you try to apply a MDAC software update |
| 30165 | You are prompted to continue the software removal process when you use Spuinst.exe and the /passive switch to remove an MDAC update |
| 30166 |
|
| 30167 | When you set the RecordSource property of an ADO Data Control to a different SQL SELECT statement and then try to execute the Refresh method, the following error is returned: Syntax error in FROM clause. which is followed by: Run-time error... |
| 30168 | Component Object Model (COM) marshaling involves two primary concepts; the passing of data from one process or thread to another, and the synchronization of threads accessing a COM object. While there are many books that detail the concepts of COM... |
| 30169 | Fixes a problem that causes an application to retrieve a bad connection from the connection pool and to generate an error while connecting to an Oracle database by using MSDAORA. Provides a list of files that are updated in the hotfix. |
| 30170 | When you attempt to disconnect an ADO Recordset by setting its ActiveConnection Object property to Nothing , the following error message might appear: Run-time error '3705': Operation is not allowed when the object is open. Only client-side ADO... |
| 30171 | When creating a new SQL Server Data Source Name (DSN) using the ODBC API SQLConfigDataSource function, a network library must be specified. If the network library name is in lowercase letters, the Client Configuration dialog box may show it as... |
| 30172 | When an ActiveX Data Objects (ADO) recordset is marshalled out-of-process while an AddNew method is pending on the recordset, the result is that strings are set to zero length strings and numeric fields are set to zero. This behavior is by design.... |
| 30173 | Fixes a problem where an access violation occurs when you bind too many parameters to an ODBC statement handle. The access violation condition occurs when the SQL_DESC_COUNT header field is set to a value that is larger than 64 KB. |
| 30174 | Describes a problem that occurs when you perform an update or an insert statement from an ODBC client application, and the contents of the ntext parameter may be corrupted when the code page is different on the client. |
| 30175 | Explains that a fix is available for a memory leak problem. This problem may occur when you use MSDAORA as a provider for retrieving data for the LONG data type by using the REF CURSOR data type in Oracle. |
| 30176 | Explains that, during the MDAC setup process, some files in the Dllcache folder may not be updated. To resolve this problem, upgrade your MDAC components to the latest version. |
| 30177 | Explains that you will see a blank help window if you try to bring up context sensitive Help for ADO 2.6 by pressing F1 since the ADO 2.6 help file is not included with the core MDAC 2.6 installation file. |
| 30178 | Explains that you may receive an error message when you try to import dates by using the bcp utility, and the day or the month contains one digit and the other contains two digits. Provides a list of files that are updated in the hotfix. |
| 30179 | The functionality to specify parameters for a T-SQL or XPath query is provided by enhancements in ActiveX Data Objects (ADO) 2.6. This article presents a sample of how to specify parameters to a templated query against SQL Server 2000 from an MDAC 2.6... |
| 30180 | When you use a single ADODB Connection object multiple times within an MTS transaction, other ADO objects must be cleaned up after use. Also, client cursors should be used when possible. If ADO objects are not cleaned up properly, ADO may raise an... |
| 30181 | When you use OLE DB with databases that support very large numeric types (for example, Oracle's NUMBER data type which supports up to 38 digits), OLE DB returns DBTYPE_VARNUMERIC as the column's data type. These large numbers can be stored and... |
| 30182 | This article describes how to attach and create Querydefs on external ODBC tables. The method for opening external ODBC tables is to attach the tables to an .mdb file. Jet does not support named QueryDefs on a non-attached ODBC database. A non-... |
| 30183 | Describes a fix for queries that are run on Oracle databases bz using the convert function and are not using the default Oracle convert type. |
| 30184 | This article demonstrates the use of a singleton SELECT to retrieve a single record from the SQL Server IRow interface from ASP. |
| 30185 | This article describes how to use the MSRemote provider to connect to and retrieve data from a remote database. The MSRemote provider allows the user to access OLE DB providers running on remote computers or in separate processes on the same computer.... |
| 30186 | This Support WebCast session provides information about the most common issues that are known to cause General Network Error error messages in client-side applications when connecting to SQL Server. |
| 30187 | The ODBC Driver Manager has a trace facility that allows the sequence of function calls made by an ODBC application to be recorded into a log file. Tracing is performed by a trace DLL, which captures calls between the application and the Driver... |
| 30188 | This article demonstrates how to use OLE DB interfaces to insert NULL data into a Microsoft SQL Server table by using a parameterized query. |
| 30189 | When you want an XML representation of a recordset you can use the new ADODB.Stream object to retrieve a string with the XML. In ADO 2.5 it is not necessary to save on a disk using the save method to retrieve the XML string generated by the recordset. |
| 30190 | Fixes the performance of the SET FMTONLY Transact-SQL query hint. |
| 30191 | The introduction of Offline views in Visual FoxPro 5.0 enabled users to work with selected data sets while disconnected from the server. Use of indexes and functions that take advantage of Rushmore Optimization provide a highly efficient method of... |
| 30192 | Often, you find a need for temporary storage for data. ADO 2. x enables you to create recordsets on the fly for this purpose. |
| 30193 | By default, when creating a view on a table, any field with a primary key index is not marked as updateable. This article illustrates how you can mark the primary key as updateable through the View Designer, and programmatically. |
| 30195 | Visual FoxPro 5.0 introduces a new SYS() function, SYS(3053), which returns the ODBC hEnv (environment handle) that Visual FoxPro uses for connectivity operations. One of the uses of the SYS() function is to get a list of available datasources that... |
| 30196 | Describes a way to prevent the ADODB.Stream object from running in Internet Explorer. You can do this to prevent a malicious Web site from using the ADODB.Stream object to exploit known security vulnerabilities in Internet Explorer. |
| 30197 | The Microsoft Internet Publishing Provider, MSDAIPP.dso, can be used to retrieve documents located in Internet Information Server (IIS) Virtual Directories. The provider can return a Recordset containing all the files in the directory, or a Record... |
| 30198 | This article is a continuation of the following Microsoft Knowledge Base article, which includes how to troubleshoot the Access Method and Microsoft Jet by changing the registry: 240377 How To Ensure Jet 3.5 Is Installed Correctly (Part I) |
| 30199 | This article describes how to get more information on the ODBC Call Failed error. When errors occur using ODBC databases, Visual Basic will provide an ODBC Call Failed error message. This generic error message provides no specific detail so you must... |
| 30200 | When you send logical data to SQL Server via the SQLEXEC() function, true (.T.) and false (.F.) values must be sent as 1 and 0. |
| 30201 | Fixes a problem that causes the SQLOLEDB provider to stop responding when the provider tries to access the sqlxmlx.dll file. Provides a list of files that are updated in the hotfix. |
| 30202 | Explains that a deadlock occurs when you repeatedly load and then unload the Dbnetlib.dll DLL in an application. Requires that you install a hotfix to resolve the problem. |
| 30203 | Remote Data Services (RDS) is a technology that allows client-side Web applications to have database connectivity. With RDS, the user can make remote calls to an ActiveX DLL that is hosted on a Web service and can use the methods of that component to... |
| 30204 | The Working with LONG, LONG RAW and VARCHAR2(2000) Oracle Datatypes white paper is intended to clarify the handling of the Oracle datatypes LONG, LONG RAW and VARCHAR2(2000) when they are used with Microsoft Visual Basic and Remote Data Objects... |
| 30205 | XMLTemplate.exe demonstrates how to extract an XML stream from a SQL Server 2000 database using an XML Template file and the ADO Command object. |
| 30206 | Provides release information about the MDAC 2.6 SP 2 Refresh (2.62.7400.1). Lists the frequently asked questions about this refresh and the known issues with this refresh. Lists all the files that are included with this refresh. |
| 30207 | Provides release information about the MDAC 2.7 Service Pack 1 Refresh (2.71.9040.2). Lists the frequently asked questions about this refresh and the known issues with this refresh. Lists all the files that are included with this refresh. |
| 30208 | Provides release information about MDAC 2.6 SP1(2.61.7326.6). Lists the frequently asked questions about MDAC 2.6 SP1 and the known issues with MDAC 2.6 SP1. Lists all the files that are included with MDAC 2.6 SP1. |
| 30209 | Provides release information about Microsoft Data Access Components 2.6 (2.60.6526.3). Lists the frequently asked questions about MDAC 2.6 and the known issues with MDAC 2.6. Lists all the files that are included with MDAC 2.6. |
| 30210 | Provides release information about Microsoft Data Access Components 2.5 SP3 (2.53.6200.2). Lists the frequently asked questions about MDAC 2.5 SP3 and the known issues for MDAC 2.5 SP3. Lists all the files that are included with MDAC 2.5 SP3. |
| 30211 | When you connect to Microsoft SQL Server 2000 or to Microsoft SQL Server 7.0, and you call the SQLStatistics ODBC function, you may notice that the collation is always returned as A regardless of the sort order sequence. You may also notice this... |
| 30212 | Provides answers to Frequently Asked Questions (FAQs) regarding the setup and installation of MDAC 2.6. |
| 30213 | Explains the cause for the behavior that occurs after the timeout expires when connected to Microsoft SQL Server by using dialup connection. |
| 30214 | Explains that when you install the MS03-033 security patch on your computer that is running the Japanese version of Windows 2000 SP3, the data source name (DSN) configuration dialog box is displayed in English. Provides a fix for this problem. |
| 30215 | Provides the information about release manifest for MDAC 2.7 Refresh (2.70.9001.0) |
| 30216 | The article explains the underlying Oracle Call Interface layer that returns an unidentified Oracle error code while using an Oracle REF CURSOR. |
| 30217 | When you pass an ActiveX Data Objects (ADO) Field object as a parameter value to the Command.CreateParameter method, a memory leak occurs. When you do this repeatedly, Performance Monitor shows a steady increase in both the private and virtual bytes. |
| 30218 | Lists all the hotfixes that are available for MDAC 2.7 SP1 in a single update file. You have to call Microsoft Product Support Services to obtain the file. |
| 30219 | This release manifest applies to the Internet release of Microsoft Data Access Components (MDAC) 2.8, referred to as MDAC 2.8 (2.80.1022.3). For information about installing, uninstalling, upgrading, and downgrading MDAC releases see the following... |
| 30220 | Explains the cause for the error that occurs when you configure a UDL file on a computer that is running on 64-bit operating system. You must install MDAC 2.8 Service Pack 1 to resolve this error. |
| 30221 | Provides a fix for an error that may occur with some OLE DB providers when you try to update a row in an ADO client-side cursor. |
| 30222 | Fixes the problem that occurs when you specify the adPersistADTG format to persist a hierarchical Recordset object to a Stream object. Requires that you install a hotfix to resolve this problem. |
| 30223 | Explains that the application may stop responding or behave unexpectedly while you run a COM+ application that uses the Microsoft ODBC Driver for Oracle. Requires that you install a hotfix to resolve this problem. |
| 30224 | When you try to connect to a data source by using the Microsoft OLE DB Provider for SQL Server, an access violation error may occur. You may notice this behavior when the Microsoft OLE DB Provider for SQL Server is initialized to prompt you for logon... |
| 30225 | Provides a fix for a problem that occurs when a long query string is used for a hierarchical ADO Recordset with MDAC 2.8. |
| 30226 | Discusses thr problem with importing data in DBCS format (such as Japanese or Korean) from a text file that is more than 32 MB to SQL Server table by using the BCP utility. This occurs if MDAC 2.8 is installed on your computer. |
| 30227 | OLEDB provider gets access violation with the DBPROMPT_PROMPT property. |
| 30228 | When you try to rollback an installation of Microsoft Data Access Components (MDAC), you receive the following error message: Fatal Setup Error Microsoft Data Access Components cannot be rolled back. Setup has detected that a different version of... |
| 30229 | When you try to fetch data that contains special characters such as carriage returns or line feed by using Microsoft ADO and the Microsoft Data Access OLE DB Persistence Provider (MSPersist), users may receive the following error message: Run-time... |
| 30230 | When you sort in multiple columns, some columns might not sort correctly if one of the columns includes a null value. |
| 30231 | If you use ODBC or DAO in the InitInstance or DLLMain functions of a DLL, your application may fail with an Access Violation or display some other unanticipated behavior. This can occur when you use the MFC Database Classes (ODBC-based or... |
| 30232 | When you use FileMon or another utility to monitor file activity, if an application uses DAO 3.6 x with Jet 4.0, you receive the following error message: FILE NOT FOUND for the following dynamic-link libraries (DLLs): MSJET49.DLL MSJET48.DLL... |
| 30233 | You can link a table from an Oracle 8 relational database management system (RDBMS) to a Microsoft Access 2000 database. However, if the Oracle table name is not in uppercase characters, you receive the following error message: The Microsoft Jet... |
| 30234 | This article provides a resolution to the error that occurs when you install Microsoft Security Update MS04-003. |
| 30235 | After you install the MS04-003 security update that is described in Microsoft Knowledge Base article 832483, you may not be able to start your computer. Instead, you may receive the following error message: The Logon User Interface DLL Msgina.dll... |
| 30236 | This article shows by example how to use Visual FoxPro and ODBC to access data that resides in ASCII text files. |
| 30237 | This article describes how the Microsoft OLE DB provider for SQL Server (SQLOLEDB) that is included with Microsoft Data Access Components (MDAC), allocates memory for the IRowset object. The article also discusses the differences in the memory... |
| 30238 | You cannot create out-of-process providers with Microsoft Data Access (MDAC) OLE DB components. |
| 30239 | Calling TABLEUPDATE() on a SQL table does not succeed in the following situation. A remote view on a SQL table contains a timestamp field, and the WhereType property of the view is set to Key & Timestamp. When updates are sent to the remote SQL... |
| 30240 | Microsoft has released security bulletin MS04-003. The security bulletin contains all the relevant information about the security patch, including file manifest information and deployment options. To view the complete security bulletin, visit the... |
| 30241 | You can use the Microsoft Access user interface to create an AutoNumber field, in which the field size can be Long Integer or Replication ID. If you select Replication ID as the field size, a globally unique identifier (GUID) is automatically... |
| 30242 | When you try to establish a connection to a named instance of Microsoft SQL Server in another domain, if an instance of SQL Server with the same named instance (and the same SQL Server name) exists in the local domain, you are connected to the... |
| 30243 | The Depth property of an instance of the Level object always returns -1 instead of the actual depth level. |
| 30244 | When you run a query with the OPENROWSET function, and you do not specify the username and password in the function, you receive the following error message: Login failed for user 'SYSTEM' |
| 30245 | During the development and test phases of any software solution, you may experience problems. These problems might be related to the code or to the configuration that you use. Typically, most of these problems are caught during the development and... |
| 30246 | If you close a recordset, and then reopen the recordset with a different lock type, an access violation may occur. |
| 30247 | When you call the ActiveX Data Objects (ADO) Parameters.Refresh function on a SQL statement that contains parameter tokens inside of a nested SELECT statement, the following error may be reported by the SQL Server OLEDB Provider and SQL Server ODBC... |
| 30248 | When you run an OLE DB or ActiveX Data Objects (ADO) application on Japanese Windows 95 or Japanese Windows 98 with MDAC 2.5 installed, Japanese error messages that are raised by the OLE DB Core Services layer are blank. When an error in the OLE DB... |
| 30249 | The SQL Server data type timestamp is a column value that is automatically updated every time a row is inserted or updated. Values in timestamp columns are not date/time data. By default, they are defined as binary(8) (for non nullable columns) or... |
| 30250 | When you use the adPromptAlways constant to open a connection to SQL Server 2000, the user receives the following error message: 'Run time error '-2147418113 (8000ffff)': Catastrophic Failure'. This problem occurs when you use a trusted connection to... |
| 30251 | When you turn on connection pooling at the process level and call the SQLManageDataSources function to configure a file data source name (DSN), you may receive the following error: General error: Invalid file dsn 'C:\Program Files\Common... |
| 30252 | An access violation may occur if you try to access the Filter property of an ActiveX Data Objects (ADO) Recordset object on a multi-processor computer under heavy load. |
| 30253 | The SQL Server native provider (SQLOLEDB) may return no data for a VARCHAR field that is larger than 255 characters under the following conditions: The properties for the rowset will create a Fast Forward cursor. The AutoFetch property (a... |
| 30254 | Client applications that call the ODBC API SQLBindCol() function to bind a Unicode data column using SQL_C_DEFAULT will be bound as SQL_C_CHAR. When you call SQLDescribeCol() on a Unicode datatype, the column's datatype will be reported as SQL_WCHAR,... |
| 30255 | On updating a row which has been newly inserted into a table, whether through an OLEDB rowset or an ActiveX Data Objects (ADO) recordset, the following error may occur: (0x80040e21, DB_E_ERRORSOCCURRED) Multiple-step OLE DB operation generated errors.... |
| 30256 | When you try to execute an extremely long query text (greater than 8000 characters) inside of an OPENQUERY function, with a linked server, you may see error messages similar to: Server: Msg 170, Level 15, State 1, Line 1 Line 1: Incorrect syntax near... |
| 30257 | When you call the ODBC function SQLConnectW and supply non-null terminated strings for the data source name (DSN), user ID (UID), or password (PWD) parameters along with length indicators indicating the exact byte length of the strings, this may later... |
| 30258 | Running a certain sequence of commands involving explicit transactions and parameters in an application program using the SQLOLEDB Provider incorrectly leaves an uncommitted transaction open. This can cause severe blocking and other problems. |
| 30259 | When ODBC connection pooling is disabled, using the following sequence in a loop does not result in a Function sequence error: SQLExecDirect SQLFetch SQLSetStmtOption (SQL_ATTR_AUTOCOMMIT,SQL_AUTOCOMMIT_OFF) SQLTransact(SQL_COMMIT) SQLSetStmtOption... |
| 30260 | When an application that uses multiple threads that share a global environment handle implements Open Database Connectivity (ODBC) connection pooling, the application may stop responding (hang) on the platforms listed above with MDAC version 2.5 or... |
| 30261 | When you use aggregate functions like DECODE() on Oracle views derieved from tables with non-null columns, NULL values can be returned. Attempting to query the value of the column or trying to perform a MoveFirst causes the following error message:... |
| 30262 | SQLBindParameter() in the SQL Server ODBC driver version 3.7x behave differently from previous releases of the driver. With SQL Server ODBC drivers prior to version 3.7x, parameter values specified with SQLBindParameter() are not padded with spaces... |
| 30264 | This article assumes intermediate knowledge of ATL, ADO and RDS technologies. This article demonstrates one way to pass an array of Recordsets from an ActiveX Data Objects (ADO)/Remote Data Service (RDS) server. |
| 30265 | The error message: ORA-00942: table or view does not exist will be seen when trying to access a table which was exported from Access 2000 using MSORCL32.DLL and the destination table is not specified using upper case letters. |
| 30266 | Opening a view that executes a long running query in the SQL Server 7.0 Enterprise Manager (SEM) will get an ODBC Timeout error. |
| 30267 | When you run a parameterized query, with a parameter of type decimal and a precision of 38, against a SQL Server 7.0 database using the 3.70 driver, you may receive the following error message: Server: Msg 2750, Level 16, State 1, Procedure... |
| 30268 | The SQL Server ODBC Driver version 3.70.06.23 and later does not support the return of an output parameter from an SQL SELECT statement. Instead, the driver returns the output parameter as a result set. For example, when executing Select ?=Max(qty)... |
| 30269 | This article describes how to retrieve numeric data from the SQL Server ODBC driver into a numeric structure and how to get the correct values using specific precision and scale values. The SQL_NUMERIC_STRUCT is defined in the sqltypes.h header file... |
| 30270 | This article presents a step-by-step troubleshooting guide for MDAC setup issues. |
| 30271 | When using the MFC Database classes or calling ODBC functions within the DLL_PROCESS_DETACH case of the DllMain() function, an access violation can occur especially if the DLL links to the MFC DLL (which does a LoadLibrary call to call ODBC). For... |
| 30272 | By default, when you use the MFC ODBC database classes to connect to a datasource, ODBC invokes a login dialog box that allows the user to type in any necessary information, such as a password, to log in. With Visual C++ 4.2, use the... |
| 30273 | The MFC Encyclopedia article Recordset: Declaring a Class for a Predefined Query describes how to invoke a predefined query that takes parameters and returns a result set. The instructions in that article will not work for predefined queries that... |
| 30274 | The ODBC Driver Manager and the Cursor Library must have the same cursor level. ODBC.DLL and ODBCCURS.DLL are the corresponding files in 16-bit Windows. ODBC32.DLL and ODBCCR32.DLL are the corresponding files in 32-bit Windows. Attempting to use these... |
| 30275 | When you disconnect a recordset that is returned from the Microsoft DataShape provider, it may appear that the recordset is disconnected. However, when the active connections are examined, the connection is still open. In some circumstances this may... |
| 30276 | This article presents a list of all the files installed by MDAC 2.0 SP2. MDAC 2.0 SP2 (Mdac_typ.exe) can be downloaded from http://msdn.microsoft.com/dataaccess . All the following locations of files are given as they were installed on Windows NT. For... |
| 30277 | This article details how to import and export tables using SQL DML (data manipulation language) statements with the Microsoft Access ODBC driver. |
| 30278 | The OLE DB database components that are included with the Microsoft Data Access Components (MDAC) 2.7 software development kit (SDK) contain some changes from earlier versions of OLE DB to allow programmers to code to the new 64-bit platforms. This... |
| 30279 | Beginning with Windows 2000, the Microsoft Data Access Components (MDAC) are considered an integral part of the operating system. As a result, the MDAC 2.5 service packs are included as part of the Windows 2000 service packs. Windows 2000 Service Pack... |
| 30280 | If CRecordset::GetFieldValue() is used on a numeric column to retrieve a value from an SQL UNION derived recordset and the Microsoft Oracle ODBC driver is used, then the following error message occurs: Error in column 1: Numeric value out of range... |
| 30281 | When you use Microsoft's Oracle ODBC driver with the ODBC SQLDescribeCol function, incorrect values may be returned for the column name and column name length. |
| 30282 | You may encounter a variety of ODBC error messages when accessing dBase databases which had been successfully accessible with prior versions of the Microsoft dBase Driver. |
| 30283 | Applications that use the Microsoft Jet Database Engine can prevent a computer that supports the Advanced Power Management (APM) or the Advanced Configuration and Power Interface (ACPI) technologies from going into Standby mode. |
| 30284 | Some queries that are based on one or more linked ODBC Microsoft Visual FoxPro tables may return inconsistent results each time that you run the queries. Examples of queries that might exhibit this behavior are queries that are based on one or more... |
| 30285 | To retrieve the value of a newly inserted Identity field, set the Open rowset DBPROP_SERVERDATAONINSERT property to True. |
| 30286 | It is possible to create a batch of SQL statements that run on Microsoft SQL Server by separating each SQL statement with a semicolon (;). You can achieve similar results when you run Oracle with either the OLE-DB Oracle Provider or Oracle driver... |
| 30287 | A Microsoft Visual C++ database project that uses the Microsoft Access 97 (Jet 3.5) ODBC Driver has a noticeable drop in performance compared to similar projects that use the Microsoft Access 95 (Jet 3.0) ODBC Driver. |
| 30288 | If an application connects to a database using the Microsoft Access ODBC Driver or the Microsoft OLE DB Provider for Jet version 4.0, and if the application uses the Now function of the Visual Basic for Applications in the WHERE clause of a SQL query,... |
| 30289 | Web developers often need to read binary files from the Web server's file system through Active Server Pages (ASP) and then send the content to the Web browser (for example, to write an Excel file to the browser). Although developers often attempt... |
| 30290 | An empty binary field formatted with rules to print text, such as Yes for True and No for False, will return an error unless nulls are allowed. |
| 30291 | When you try to use the Query Designer against the MS Shape Provider in the Data Environment, the following error message is returned: Query Designer encountered a ADODB.Properties error: Query Designer encountered a ADODB.Properties error: Query... |
| 30292 | The purpose of this article is to help you understand how the Visual Basic 6.0 Package and Deployment Wizard (PDW) distributes the Microsoft Data Access Components (MDAC) in order to allow you to control which version of MDAC is distributed with your... |
| 30293 | When using the Microsoft ODBC Driver for Oracle, NUMERIC fields that have been defined with a null or odd scale but are bound as a character ODBC datatype (such as SQL_C_CHAR) are returned with a trailing zero appended to the decimal portion of the... |
| 30294 | When using the Microsoft SQL Server ODBC driver (sqlsrv32.dll) in a manner that permits multiple concurrent statement handles on a single connection, a busy connection may leave cursors open in the SQL Server database with no warnings or notifications... |
| 30295 | When you use the Microsoft SQL Server ODBC driver and you use SQLSetPos to insert or update date or time values that contain the maximum allowable values for the hour, minute, second and millisecond portions (such as 1999-10-03 23:59:59:999), the... |
| 30296 | If you use the Microsoft ODBC Driver for SQL Server to execute a stored procedure that inserts multiple rows into a SQL Server table, an inconsistent number of records may be inserted. This problem can occur when all of the following conditions are... |
| 30297 |
The RLockMFC.exe sample program demonstrates how to use the Microsoft Foundation Class (MFC) CDatabase and CRecordset objects with SQL Server in a Visual C++ application to pessimistically lock individual rows within a recordset while they are being... |
| 30298 | When you create or configure ODBC data source names (DSNs) using the Microsoft SQL Server ODBC driver, issues such as the following may occur: Switching of Net-Library protocols. A new DSN's protocol is used for older DSNs, or vice versa. |
| 30299 | When running Oracle Stored Procedures that use 10 or more output parameters, you receive an Access Violation or ActiveX Data Objects (ADO) error. Two sample errors follow: Access Violation (0xC0000005) in ORA804.DLL @01B20002. -or- Microsoft OLE DB... |
| 30300 | When you try to update SQL Server 7.0 tables that contain Unicode datatypes from Access 97 or Access 95 using the 3.60.0319 (or earlier) version of the ODBC SQLServer driver, the following error message appears: [Microsoft][ODBC SQLServer... |
| 30301 | OLE DB Services are used in a variety of ways, and the error that is returned by this bug depends on the situation. This article describes some of the possible uses and the errors that may result. on how to load the OLE DB Services 223333... |
| 30302 | When you use Microsoft SQL Server ODBC driver version 3.70.0623 or 3.70.0690, and call the SQLPrepare function on a statement similar to the following: SELECT A.title_id FROM titles A WHERE A.title_id IN (?) GROUP BY A.title_id UNION SELECT B.title_id... |
| 30303 | When you attempt to connect to a SQL Server through TCP/IP on a Windows 98 client, the following error message can occur: Assertion failed! Program: C:\WINDOWS\RUNDLL32.EXE File: ../src/sqlsspi.c Line: 120 Expression: Count For information on how your... |
| 30304 | When using an SQL statement with a WHERE clause that contains a test for NULL using the = operator, records that match the query are not returned in the recordset. This happens with Jet 4.0 when using DAO, ODBC or OLE DB. Here are a few examples of... |
| 30305 | OLE DB resource pooling, also known as OLE DB session pooling, is handled by the OLE DB core components. To take advantage of resource pooling, an OLE DB consumer must invoke the data provider by using either the IDataInitialize or the... |
| 30306 | When using the SQL Server OLE DB provider and OLE DB consumer Templates with a SQL Server database, calling CRowset::SetData() on the CCommand object to update a record returns DB_ERRORSOCCURRED when the table contains an identity column and the... |
| 30307 | When attempting an ActiveX Data Objects (ADO)/ Remote Data Services (RDS) update, using the OLEDB provider for ODBC (MSDASQL) with a third party ODBC driver, you may receive an error. |
| 30308 | Visual Studio 6.0 and the Data Access 2.0 Software Development Kit (SDK) both install a version of the SQL Server ODBC Driver (and OLE DB Provider) that is more current than the file found in the latest SQL Server Service Pack. Additionally, neither... |
| 30309 | When the Microsoft OLE DB Provider for SQL Server (SQLOLEDB) creates implicit connections, these connections are not pooled. The provider creates implicit connections under the following two situations: If you create additional sessions from the same... |
| 30310 | When you try to execute a distributed query by using the Microsoft SQL Server OLE DB provider, the following error might occur: One or more properties could not be set on the query for OLE DB provider 'SQLOLEDB'. |
| 30311 | When you select character data of Text data type through the OPENXML rowset provider, the text data may be truncated, or the following error message may be returned: Server: Msg 6603, Level 16, State 1 XML parsing error: System error: 265926. If the... |
| 30312 | This article demonstrates how to programmatically retrieve an XML data stream from a SQL Server 2000 mapping schema by using an XPath query. The scope operates in a client/server (2-tier) model. This sample also allows you to test XPath queries... |
| 30313 | The Open Database Connectivity (ODBC) API contains a function called SQLDataSources() which can be used to retrieve information about data sources which are available to an application. Below is a sample function which fills a CStringList with the... |
| 30314 | An OLE DB Provider created using the Visual J++ 6.0 and the OLE DB Simple Provider Toolkit does not work reliably. When attempting to use such a provider from ActiveX Data Object (ADO) via the Recordset.Open() method, the following error occurs:... |
| 30315 | There are two different methods for performing updates and inserts. One way is to create a recordset and then insert/update its records. The other way is to use the Execute method to issue a SQL statement which inserts/updates the records. |
| 30316 | Active Server Pages (ASP) applications written with ActiveX Data Objects (ADO) that pass the ADO ConnectionString property using either HTTP POST or GET fail to connect. |
| 30317 | You may receive the following error running a Remote View after setting a filter condition for a bit field from a SQL Server table: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server] Line 1: Incorrect syntax near '.'. -or-... |
| 30318 | If you try to access a field of an ADO Recordset whose source is a SQL SELECT statement that retrieves 255 columns from a Visual FoxPro table, you receive the following error message: Run-time error '-2147467259(80004005)': [Microsoft][ODBC Visual... |
| 30319 | When committing a new record to a remote view, you may receive this error: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server] The column xxx in table yyy may not be null. Where xxx is the name of the remote data's field and... |
| 30320 | Beginning with Microsoft Data Access Components (MDAC) 2.1, the Microsoft OLE DB Provider for Oracle implements the use of ROWIDs for unique row identification. This may generate some unexpected side effects in some circumstances. |
| 30321 | When installing Microsoft Data Access Components (MDAC) 2.6 RTM (version 2.60.6526.3) on computers that have 32 processors, the following error may occur when Msxml2.dll is registered: A dynamic link library (DLL) initialization routine failed This... |
| 30322 | When using parameter binding to insert negative (B.C.) dates through the Microsoft ODBC Driver for Oracle, the following error is thrown: SQLState = 22007 NativeError = 0 [Microsoft][ODBC Driver for Oracle]Error in parameter 1: Datetime field overflow... |
| 30323 | When you attempt to update or insert records into an Oracle8i server by using a NUMBER(x,y) datatype field, you receive the following error: [Microsoft][ODBC Driver for Oracle][Oracle]ORA-01722: invalid number |
| 30324 | Running a Visual Basic application using the Microsoft RDS Data Factory to access Index Server 2.0 can generate the following errors: Run-time error '-2147217887 80040e21': Errors Occurred. |
| 30325 | When using the Java Database Connectivity (JDBC) - Open Database Connectivity (ODBC) bridge to insert or update dates prior to 01-01-1900 into SQL server (version 6.5 and 7.0), the following error occurs consistently: 22008 [Microsoft][ODBC SQL... |
| 30326 | In systems that do not have MDAC 2.1 installed on them, when you use the FoxPro ODBC ISAM Driver (named Microsoft FoxPro Driver(*.dbf) in the ODBC Administrator) for 2.5 or 2.6 tables, it allows you to view the contents of a table created in Visual... |
| 30327 | After installing the Microsoft Data Access 2.0 SDK, the following errors may occur when trying to perform a SQL Server 7.0 distributed query: Server: Msg 7302, Level 16, State 1 Could not create an instance of OLE DB provider 'the_ole_db_provider'... |
| 30328 | This article provides a list of valid SQLConfigDatasource settings for the Microsoft ODBC Driver for Oracle, version 1.0 (Msorcl10.dll) and the Microsoft ODBC Driver for Oracle, version 2.0 (Msorcl32.dll). Note that the Msorcl10.dll ODBC driver... |
| 30329 | When you use the Remote Data Objects (RDO) version 2.0 in either Visual Basic 5.0 or Visual Basic 6.0, with an Oracle 7.x or 8.x database, using the Microsoft ODBC for Oracle driver, the AbsolutePosition property of the rdoResultset object produces... |
| 30330 | If you load Microsoft Office 97 prior to loading Visual FoxPro version 3.0 or 5.0 you receive the following error messages during the Visual FoxPro installation: Unable to load installable ISAM Can't load mspdox35.dll (error code=[error code]).... |
| 30331 | Using the Microsoft OLEDB Provider for SQL Server (SQLOLEDB) that comes with Microsoft Data Access Components (MDAC) version 2.6 or 2.6 SP1, when you set the value of the SSPROP_ENABLEFASTLOAD property to true in the SQLSERVERDATASOURCE property set,... |
| 30332 | When you call the Update method of an ActiveX Data Objects (ADO) recordset that is opened on a SQL statement that also contains a sub-select using the Microsoft ODBC Driver for Oracle, then the following error message occurs: [Microsoft][ODBC driver... |
| 30333 | If you use the ADOX Catalogs collection and the Microsoft OLE DB Provider for Jet to retrieve the columns of a Microsoft Access table, the columns are sorted alphabetically. |
| 30334 | The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products. Both the... |
| 30335 | You are using the Visual FoxPro ODBC driver on a non-U.S. English version of Microsoft Windows 95 or Windows 98, or on Microsoft Windows NT with the regional settings set to something other than English (United States). Attempting to issue a SQLEXEC()... |
| 30336 | When attempting to create a DSN using the installable ISAM ODBC Driver for FoxPro, the following message appears: The Microsoft FoxPro driver is no longer supported, and has been replaced by the Microsoft Visual FoxPro driver. When attempting to use... |
| 30337 | When you insert a date prior to the year 1753 by using Microsoft Access ODBC Driver, the following error message is displayed: [22008] [Microsoft][ODBC Microsoft Access Driver]Datetime field overflow (null) |
| 30338 | When trying to connect to an Access .mdb file, an ODBC error is returned stating Disk or Network Error. The Microsoft OLE DB Provider for the Microsoft Jet database engine may also return an Unspecified error (error code = 0x80004005) message. The... |
| 30339 | When using parameter binding in the Microsoft Oracle ODBC driver to insert decimal values into an Oracle server installed on UNIX, the following error is returned: [Microsoft][ODBC driver for Oracle][Oracle]ORA-01722: invalid number This error does... |
| 30340 | The Microsoft ODBC Driver for Access and the Microsoft OLE DB Provider for Jet do not provide support for bit-wise operations in SQL statements. Attempts to use AND, OR, and XOR with numeric fields in a SQL statement return the result of a logical... |
| 30341 | The Microsoft Oracle ODBC Driver versions 2.0 and 2.5 do not support synonyms for Oracle stored procedures. |
| 30342 | Microsoft OLE DB Provider for SQL Server does not support nested transactions, and the following error message is returned: Could not start a transaction for OLE DB provider '%ls'. Microsoft SQL Server also returns the following error message if the... |
| 30343 | When you use Distributed Component Object Model (DCOM) to connect to an ActiveX EXE file that connects to a Microsoft Jet database on a different server, you receive the following error message: 80004005 The Microsoft Jet database engine cannot open... |
| 30344 | When using the Microsoft ODBC for Oracle driver that ships with MDAC 2.5 or 2.6, establishing a connection to an Oracle database may take a long time (approximately 11 seconds) on the platforms listed above. This problem does not occur on Microsoft... |
| 30345 | The Microsoft Data Access Components (MDAC) version 2.1 installs the Microsoft Jet 4.0 database engine. The Microsoft Jet database engine is used by the Microsoft Access ODBC Driver, the Microsoft Jet OLE DB Provider, and the Microsoft Data Access... |
| 30346 | When using the Microsoft Oracle ODBC driver (Msorcl32.dll) provided with the Microsoft Data Access Components (MDAC) 1.5x and more than 64K of data is returned to the client computer in a scrollable or keyset driven recordset, temporary files may be... |
| 30347 | When you try to use table aliases in SELECT statements with the Microsoft Oracle ODBC driver and you are using the Keyset cursor type, you receive the following error: [Microsoft][ODBC driver for Oracle]Cannot use Keyset-driven cursor on join, with... |
| 30348 | There are several ways to change a Microsoft Access table name in a Visual Basic application, some of which include the use of SQL, OLE automation, or Microsoft ActiveX Data Objects Extensions for Data Definition Language and Security (ADOX). The... |
| 30349 | Installation of Microsoft Data Access Components (MDAC) version 2.5 or version 2.6 on a Microsoft Windows NT 4.0-based computer or a Microsoft Windows 2000-based computer may fail with one of the following error messages: Error Registering the OCX... |
| 30350 | The Microsoft OLE DB Provider for SQL Server (SQLOLEDB) is slower in inserting or updating BLOB data types such as text , ntext , or image when compared with the Microsoft OLE DB Provider for ODBC drivers (MSDASQL). |
| 30351 | After you install Microsoft Data Access Components (MDAC) 2.5 on a Microsoft Windows 95/98 or Microsoft Windows NT 4.0 computer, a Windows Setup dialog box appears after every restart, indicating that the MDAC components are being configured. On... |
| 30352 | Microsoft Data Access Components (MDAC) 2.5 is the earliest version of MDAC that can be installed on a Microsoft Windows 2000-based computer. |
| 30353 | When you call an Oracle procedure that returns an ADO recordset through the Microsoft ODBC driver for Oracle, one of the following error messages may occur: Microsoft OLE DB Provider for ODBC Drivers (0x80040E14) [Microsoft][ODBC driver for... |
| 30354 | Queries that show as fully optimized in Microsoft Visual FoxPro might run very slowly through the Microsoft Visual FoxPro ODBC driver. |
| 30355 | The Microsoft Oracle driver returns the following error message when user rights are granted and then revoked on a table accessed by a stored procedure: Return: SQL_ERROR=-1 szErrorMsg=[Microsoft][ODBC driver for Oracle]Wrong number of parameters... |
| 30356 | With Microsoft Data Access Components (MDAC) version 2.6 and later installed on the platforms listed above, the SQLBrowseConnect ODBC call enumerates Microsoft SQL Server 2000 instances but cannot enumerate Microsoft SQL Server 7.0 servers. |
| 30357 | You can use IRowsetIndex::Seek() to quickly search an indexed column. The Jet 4.0 OLE DB provider natively supports the IRowsetIndex interface, while the Microsoft SQL Server OLE DB Provider, Microsoft OLE DB Provider for Oracle, and other Microsoft... |
| 30358 | This article discusses low-level ODBC API issues and MFC programming considerations for improving the performance of applications that use the Microsoft Access ODBC driver versions 2.x or above. If you are using Visual C++ 4.0 or higher, you can also... |
| 30359 | In the Microsoft Open Database Connectivity (ODBC) Driver for Oracle, error messages greater than 255 characters are randomly truncated. The number of characters returned to the application may vary depending on the number of characters in the error... |
| 30360 | OLE DB specification doesn't provide interfaces to compact or repair databases. However, the OLE DB Provider for Microsoft Jet version 4.0 exposes this functionality through a custom interface: IJetCompact (TDataSource cotype). IJetCompact is defined... |
| 30361 | The Microsoft 32-bit ODBC drivers fail when called from a 16-bit application through the ODBC thunking layer. Particularly under Windows 95 and Windows 98, you will not be able to connect without the application failing. |
| 30362 | Data from a Microsoft Access database can be used in Visual FoxPro by creating an ODBC data source and a remote view. The ODBC data source must be created using the ODBC Administrator, and the remote view can be created interactively using the View... |
| 30363 | When a SELECT DISTINCT statement is used with the Microsoft ODBC for Oracle driver, the following error may occur: DIAG [HYC00] [Microsoft][ODBC driver for Oracle]Cannot use Keyset-driven cursor on join, with distinct clause, union, intersect or minus... |
| 30364 | Failures occur when Active Server Pages (ASP) code accesses a file-based resource over the network. Examples include the following: If you Scripting.FileSystemObject to access a file that is stored on a network share, you receive the following error... |
| 30365 | When you use data access technologies such as Microsoft Data Access Objects (DAO) or Microsoft ActiveX Data Objects (ADO) to open text files that contain a non-standard delimiter (such as a single quotation mark), the delimiter appears in the field... |
| 30366 | Microsoft Works 4.5a incorrectly installs the following OLE DB component Dynamic-Link Libraries (DLLs) into the Windows system folder (for example, C:\Winnt\System32) instead of the proper location. The following files should be placed in... |
| 30367 | When you use Visual Basic Scripting Edition (VBScript) to perform a numeric comparison or calculation on an adNumeric (131) field type, you may receive the following error messages: Microsoft VBScript runtime error '800a000d' Type mismatch -and-... |
| 30368 | When you use ActiveX Data Objects (ADO) or ODBC to open a database connection in an Active Server Pages (ASP) page, you may receive the following error message: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Driver... |
| 30369 | The following error may occur when you use DEConnection in a Visual Basic COM object running under ASP: Run-time error '-2147467259 (80004005)': [Microsoft][ODBC DriverManager] Only SQL_DRIVER_NOPROMPT is allowed when connection pooling is enabled |
| 30370 | Active Server Pages (ASP) and ActiveX Data Objects (ADO), Internet Information and Microsoft Windows NT Server version 4.0, connections to an ORACLE/Sybase database on an UNIX system may fail with an ASP Error 0115. |
| 30371 | One of the following errors occurs when passing a date to a SQL Stored Procedure: Microsoft OLE DB Provider for ODBC Drivers error 80004005 At least one parameter contained a type that was not supported. -OR- Microsoft OLE DB Provider for ODBC Drivers... |
| 30372 | When opening a connection in Active Server Pages (ASP) code to SQL Server on a separate computer from the Web server, one of these similar error messages may appear: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL... |
| 30373 | When use ActiveX Data Objects (ADO) through Active Server Pages (ASP) to connect to Microsoft SQL Server, you may receive the following error message: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver][SQL... |
| 30374 | When you use ActiveX Data Objects (ADO) and ODBC to try to connect to a Microsoft Access database, you may receive the following error message: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access 97 Driver]... |
| 30375 | When you use ActiveX Data Objects (ADO) or ODBC to connect to a Microsoft Access database, you may receive the following error message: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access 97 Driver] The... |
| 30376 | The Jet OLE DB version 4.0 provider supports the SELECT @@Identity query that allows you to retrieve the value of the auto-increment field generated on your connection. Auto-increment values used on other connections to your database do not affect the... |
| 30377 | This article explains how to insert and retrieve RAW or LONG RAW data from an Oracle database for use in an Active Server Pages (ASP) page. |
| 30378 | The sample code in this article demonstrates how to extract the value of summary rows using ADO. Summary rows are produced when you use a COMPUTE BY clause with any row aggregate functions in a SQL statement. These summary values appear as additional... |
| 30379 | ActiveX Data Objects (ADO) cause Windows 95 to stop responding with Personal Web Server (PWS) under heavy loading conditions. |
| 30380 | The following is an example of an Active Server Pages (ASP) script that can be used to troubleshoot connection problems with ODBC datasources. This example can also be used to demonstrate how to write simple scripts that select data from databases:... |
| 30381 | This article shows by example how to extract the bitmap photos in the Microsoft Access 97 Nwind.mdb database, and view them from a Web browser using Active Server Pages (ASP). In order to accomplish this task, an ActiveX DLL must be created that... |
| 30382 | If you are using ADO within components that are running under Microsoft Transaction Server (MTS), and the components have different transactional contexts, additional connections may be opened to database server. Connections opened in a package with... |
| 30383 | When you use an Active Server Pages (.asp) page and ActiveX Data Objects (ADO) to open a recordset from a query in a Microsoft Access database, which contains any intrinsic functions (for example, Month(), Left(), etc.), the following error may occur:... |
| 30384 | Beginning with Microsoft Data Access Components (MDAC) version 2.0, the Remote Data Services (RDS) components support the concept of an RDS handler. By using RDS handlers, you hide the actual connection string and query string from the user. You can... |
| 30385 | When you attempt a parameterized insert of an SQL_LONGVARBINARY (adLongVarBinary) data type with the ActiveX Data Objects (ADO) command object, the following error message may be returned: Type is Invalid This problem occurs with the Microsoft Visual... |
| 30386 | One of the following errors occurs when you update a table record from an Active Server Pages (ASP) page through ADO's Recordset.update method: Source: Microsoft OLE DB Provider for ODBC Drivers Error Number: -2147467259 Description: The query is not... |
| 30387 | The WriteText method of an ADO Stream object whose charset property is set to ascii fails after you install Microsoft Data Access Components (MDAC) 2.6 on a computer that is running Microsoft Windows 98, Windows NT 4.0 Workstation, or Windows NT 4.0... |
| 30388 | The following error message may appear when an Active Server Page (ASP) is executing the OPEN method to an Oracle data source: Microsoft OLEDB Provider for ODBC Drivers error '80004005' [Microsoft][ ODBC driver for Oracle ][Oracle ]ORA-00000: normal,... |
| 30389 | When you perform a numeric comparison or calculation on an adNumeric (131) field type using VBScript, the following errors may be returned: Microsoft VBScript runtime error '800a000d' Type mismatch Microsoft VBScript runtime error '800a01ca' Variable... |
| 30390 | You may encounter the following common error when you use ActiveX Data Objects (ADO) with Active Server Pages (ASP): Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access 97 Driver] Operation must use an... |
| 30391 | This article describes the steps that you should use while performing distributed transactions under Microsoft Transaction Server (MTS) when you use the IBM DB2 ODBC driver version 6.01 or later. This article assumes that you are developing COM... |
| 30392 | When you use the Microsoft Remote provider to run a parameterized query against a remote database, the Requery method of the ADODB.Recordset object fails with the following error message: Unknown Error (80040e4b). |
| 30393 | According to Microsoft Knowledge Base article 275561 ACC2000: New Features in Microsoft Jet 4.0: To minimize the impact of the increased page size and respond to a long-standing request from developers building applications based on the Microsoft... |
| 30394 | The Microsoft Access ODBC Driver, version 3.51.1713, which is provided with the Microsoft Data Access Components version 2.0, leaks memory when opening a connection, performing a query on that connection, and then closing the connection. |
| 30395 | When executing a parameterized query that contains a subquery, when using the Microsoft Open Database Connectivity (ODBC) Driver for Access, various unexpected problems occur. Reported problems include unexpected results (no records returned or the... |
| 30396 | Existing code that successfully inserts records into a Date field in an Oracle table breaks when upgrading the Microsoft ODBC driver for Oracle from version 2.00.XXXX (Msorcl10.dll) to version 2.573.XXXX (Msorcl32.dll). For example, the following... |
| 30397 |
|
| 30398 | This article demonstrates how to call an Oracle package to retrieve a recordset using ADO on Active Server Pages (ASP). This article assumes that: You are proficient with Visual Basic Scripting Edition (VBScript), ActiveX Data Objects (ADO), and... |
| 30399 | When you run the default Web site out-of-process and use Remote Data Services (RDS) the following error results: A Runtime Error has occurred. Do you wish to Debug? Line: xx Error: Unexpected error (0x80070558) |
| 30400 | When you view an Active Server Pages (ASP) page that uses ADO to access a database, you may find that nothing is written to the page or you may receive the following error message: error 'ASP 0115' Unexpected error /webapp/pagename.asp A trappable... |
| 30401 | When you install Windows 2000 SP1 (MDAC 2.5 SP1) or Windows 2000 SP2 (MDAC 2.5 SP2) on a system that has MDAC 2.6 installed, the resulting system configuration will have MDAC 2.6 still installed along with updated Microsoft Jet components. |
| 30402 | After upgrading to Microsoft Data Access Components (MDAC) 2.0, some queries to a Sybase database using an Intersolv 3.x Sybase ODBC driver result in the following error: ASP 0101: 80070057 Unexpected error |
| 30403 | Incorrect CREATE TABLE statements are created when Microsoft Jet database engine 4.0 exports tables through ODBC drivers that do not require identifier quote characters. If an ODBC trace is generated, a you see a statement similar to the following:... |
| 30404 | Microsoft has created new Paradox and dBASE ISAM drivers for Microsoft Jet 4.0 that do not require the installation of the Borland Database Engine (BDE) to provide full read/write access to Paradox and dBASE files. The current Jet 4.0-based Paradox... |
| 30405 | When you run a SQL query containing more than 22 UNION statements using Microsoft Jet 4.0 the following error appears: Not a valid alias name. The same query worked without error when using Microsoft Jet 3.x. |
| 30406 | A floating point exception occurs inside a process and you do not reset the floating point flags by using the _fpreset function. When you then open a Microsoft ActiveX Data Objects (ADO) 2.8 Recordset, a seemingly unrelated floating point exception... |
| 30408 | When you run a search, Index Server may return the following error message: Microsoft OLE DB Service Components error '80040e21' Errors occurred |
| 30409 | The dBASE database driver works in one of the following two modes: The latest Microsoft Jet 4.0 service pack or the Borland Database Engine (BDE) is installed. Neither the latest Jet 4.0 service pack or the BDE is installed. The dBASE data is only... |
| 30410 | When inserting records into a Microsoft Access database, immediately attempting to reselect them occasionally does not return all inserted records. This occurs even when the records are inserted and reselected on the same connection. The problem... |
| 30411 | Normally, when using ActiveX Data Objects (ADO) in Visual FoxPro, code is written to make a call to an ODBC driver, which then retrieves the data. The same result can be accomplished interactively in a Visual FoxPro form by using the ADO Data control... |
| 30412 | ADOCtl.Exe is a sample that contains ADOControls, a class library containing controls that can be bound to an ActiveX Data Objects (ADO) recordset. Using these controls, a developer can create forms that can access and update ADO recordsets. |
| 30413 | This article demonstrates how to retrieve a single record from SQL Server by using the IRow interface with a singleton SELECT . The main purpose for this technique is to avoid the overhead of creating a recordset when you are fetching a single record.... |
| 30414 | Client computers that have Microsoft Data Access Components (MDAC) version 2.6, or later, can try multiple protocols or Interprocess Communication (IPC) mechanisms to establish connections to SQL Server. |
| 30415 | When you install SQL Server 2000 Service Pack 3 (SP3), SQL Server deploys version 2000.80.380.0 of the Sqlunirl.dll file. Version 2000.80.380.0 is part of Microsoft Data Access Components (MDAC) 2.7 Service Pack 1 (SP1). The correct version... |
| 30416 | If you use the MFC (Microsoft Foundation Classes) ODBC wrapper classes (for example, CDatabase and CRecordset ) on one thread, and you use straight ODBC API calls on another thread in the same process, a deadlock may occur. |
| 30417 | Microsoft Data Links provide an easy way to create or validate a Microsoft ActiveX Data Objects (ADO) connection string that uses an ODBC driver or an OLE DB Provider to connect to a given data source. This article describes how to set up and use this... |
| 30418 | Beginning with Windows 2000, the Microsoft Data Access Components (MDAC) are considered an integral part of the operating system. As a result, the MDAC 2.5 service packs are included as part of the Windows 2000 service packs. Windows 2000 Service Pack... |
| 30419 | On a computer running Windows NT 4.0 with Microsoft Data Access Components (MDAC) 2.5 or 2.6 installed, you may receive the following error message when you attempt to open HTML Help files: You need a newer version of HHCTRL.OCX to be able to read... |
| 30420 | After you install the Microsoft Data Access Components 1.5 through 2.1, you need to restart your computer. After you restart, you might receive the following error message: Unable to open response file c:\temp\odbcconf.tmp |
| 30421 | Rs2dbf.exe is a sample file that shows how to convert an ActiveX Data Objects (ADO) recordset to a Visual FoxPro cursor. This self-extracting executable contains a Visual FoxPro program called Rs2dbf.prg and the necessary ADO include files. Running... |
| 30422 | This article describes how you can check the version of ActiveX Data Objects (ADO) you have installed on your computer. |
| 30423 | Under some circumstances, you may need to modify the properties of a connection at run time. This article describes each of the properties and the default values of a connection. The sample code illustrates how to create a connection and use the... |
| 30424 | This article discusses what is required in order to use the FoxPro SQLPrepare() function. |
| 30425 | OLEDBSQLXML.exe demonstrates how to create an ATL OLE DB client that extracts an XML Stream from a SQL 2000 Server using a SQL XML Query. |
| 30426 | When you try to specify a connection string to use the persist provider to open from a valid ADO stream object, you receive the following error message: Run-time error '3001': Arguments are of the wrong type, are out of acceptable range, or are in... |
| 30427 | By default, ADO uses OLEDB session pooling to maintain a pool of connections to the database. In some cases, you might want to use ODBC connection pooling instead of OLEDB session pooling. This article describes what is necessary to enable ODBC... |
| 30428 | Microsoft Visual Basic crashes when appending a newly-created column to a table by setting the ParentCatalog property of a column to an active catalog and adding it to an existing table. |
| 30429 | When you use the SQL Server ODBC driver version 2000.080.0194, which was released with SQL Server 2000 and Microsoft Data Access Components (MDAC) 2.6 RTM, the authentication settings for ODBC data source names (DSNs) are ignored. The driver attempts... |
| 30430 | When Using ActiveX Data Objects (ADO) and AppendChunk , Microsoft OLE DB Provider for Oracle truncates data that is being inserted into LONGRAW and LONG datatypes. Approximately 40K inserts into a LONGRAW field, while about 64K inserts into a LONG... |
| 30431 | This article contains sample code for an ASP that adds a new record to a Microsoft Visual FoxPro (VFP) table and inserts over 254 characters into a memo field in that table. |
| 30432 | When you create remote views using SQL Server tables as the data source, Visual FoxPro automatically sets the KeyField property to .T. for columns that are included in a primary index key. In some instances, you might want to retrieve the primary key... |
| 30433 | When you use the oj outer join syntax with a parameter in a SELECT statement using the Microsoft SQL Server driver with a SQL Server 6.5 back end, the following error message is returned: [Microsoft][ODBC SQL Server Driver]COUNT field incorrect or... |
| 30434 | When using an MDAC 2.1 version of the Microsoft Access ODBC driver and opening a Microsoft Access database file on a network share, an excessive amount of network packet activity occurs, even when the ODBC connection is idle. In addition, when using a... |
| 30435 | An empty recordset is returned when you use Remote Data Objects (RDO) to pass a character type parameter from Microsoft Visual Basic to Microsoft Access. |
| 30436 | The ODBC Microsoft Desktop Database Drivers Help documentation contains an error for the ODBC Microsoft Access Setup. The Page timeout in the Options section is incorrect. |
| 30437 | Both the Microsoft ODBC Driver for Oracle, version 2.573.2927, and the Microsoft OLE DB Provider for Oracle, version 2.0.3002.15, shipping with the Microsoft Data Access Components (MDAC) version 2.0 have handle leaks, which lead to memory leaks. MDAC... |
| 30438 | When you attempt to add a system or user data source name (DSN) to a Microsoft Access database, the ODBC Microsoft Access Setup window may not appear after you select Microsoft Access driver from the drivers listed in the Create New Data Source window. |
| 30439 | The following information is from the Data Access Software Development Kit (SDK) version 2.0 OLREADME file: IRowsetResynch is an interface defined in OLE DB 1.x that allows consumers to retrieve the current values for rows that may have been changed... |
| 30440 | This article describes how to programmatically specify the client network library in the connection string when you connect to a SQL Server database. In Microsoft Data Access Components (MDAC) 2.6 and later, you can specify the client access library... |
| 30441 | When you upgrade from Microsoft Data Access Components (MDAC) 2.6 (that is included with SQLXML 2.6) to MDAC 2.7 (that is included with SQLXML 3.0), you find that GUID data that is retrieved through SQLXML does not contain opening and closing braces (... |
| 30442 | When you are trying to use Microsoft Data Access Components (MDAC) in your applications, you may receive one of the following error messages: Error in the DLL. -or- Provider can not be found. Ensure that the provider has been installed properly. -or-... |
| 30443 | When you try to connect to a Microsoft SQL Server named instance by using a Canonical Name (CNAME), the client receives the following error message, and the connection fails: SQL Server does not exist or access denied ConnectionOpen (Connect()) |
| 30444 | Dbf2rs.exe is a self-extracting executable that contains a Visual FoxPro program named Dbf2rs.prg, which shows how to convert a Visual FoxPro cursor to an ActiveX Data Objects (ADO) recordset. The executable file also contains the necessary ADO... |
| 30445 | After installing Microsoft Data Access Components (MDAC) version 2.5 or later, the open and close performance of a single connection to the Microsoft ODBC for Oracle driver is noticeably slower. This impacts the performance of typical single... |
| 30446 | While Visual FoxPro has the ability to import a number of different file formats, it is not possible to import a Microsoft Access database directly into Visual FoxPro. You must use ODBC. |
| 30447 | This article gives example SQL SELECT statements that you can use against Microsoft Excel versions 4.0 and 5.0 worksheets in Visual FoxPro by using ODBC. |
| 30448 | Attempting to open a Visual FoxPro version 3.0 table in Microsoft Excel version 5.0 or 7.0 results in this error: Cannot read this binary file. |
| 30449 | This article describes how to create a data source to access Microsoft Excel files by using ODBC. |
| 30450 | STonSel.exe demonstrates how to configure an ADO 2.6 client to retrieve one row of data from a SQL Server 2000 database. |
| 30451 | If you persist a recordset with empty values at non-nullable columns to an Extensible Markup Language (XML) file by using the Save Method of an ADO Recordset, incorrect data is saved, and no error occurs. |
| 30452 | The Paradox database driver works in one of two modes. One mode is when either the Microsoft Jet 4.0 Service Pack 5 (SP5) or the Borland Database Engine (BDE) is installed. The other mode is when neither of these are installed. Paradox data is only... |
| 30453 | When you try to link a password-protected Paradox file from an Access 2000 database by using the Paradox ISAM, you may receive one of the following errors: Unexpected error from external database driver (10498). -or- Invalid Index Definition, so... |
| 30454 | When you use a LIKE clause on a column in a query, and the column has Double-Byte Character Set (DBCS) characters, not all the records that meet the criteria are returned. |
| 30455 | You notice that the wrong record is found when you use the Find dialog box or when you run any Data Access Object (DAO) Find methods. These methods may be one of the following: FindFirst , FindLast , FindNext , or FindPrevious . |
| 30456 | When you use a LIKE clause on a column in a query, and the column has Double-Byte Character Set (DBCS) characters, not all records that meet the criteria are returned. |
| 30458 | The redistribution for Microsoft Data Access Components (MDAC) version 2.x is essentially a setup program encapsulated within another setup program. The outer setup provides a single .exe which, when run, extracts the contents needed for the inner... |
| 30459 | Both SQL Server authentication (standard security) and Windows NT authentication (integrated security) are SQL Server authentication methods that are used to access a SQL Server database from Active Server Pages (ASP). Note This article does not apply... |
| 30460 | Under certain circumstances, if you call the Requery method of an ActiveX Data Objects (ADO) Recordset object, the LockType property of the Recordset changes to read-only ( adLockReadOnly ). This problem may occur under the following circumstances: If... |
| 30461 | Using Remote Data Services (RDS), specifically the RDS.Dataspace object, you can invoke remote business objects residing on a Web server running Internet Information Server (IIS). When these components are instantiated through the RDS.Dataspace... |
| 30462 | When running multithreaded ActiveX Data Objects (ADO) code under high stress on a multiprocessor computer, an access violation (AV) may occur when closing an ADO Recordset . Examination of the call stack at the time of the AV (with the appropriate... |
| 30463 | This article outlines some of the common steps to take when you troubleshoot a problem with a connection to an Oracle Database from an Active Server Pages (ASP) application. Some of the more common error messages are: Microsoft OLE DB Provider for... |
| 30464 | With Microsoft Visual Basic versions 4.0, 5.0, and 6.0 for Windows, you can specify your ODBC (Open Database Connectivity) driver and server in your connect string when using RDO (Remote Data Object) and DAO (Data Access Objects) which eliminates the... |
| 30465 | This article describes the functionality of the Microsoft Component Checker (ComCheck). The ComCheck tool can help you to diagnose installation issues with Microsoft Data Access Components (MDAC). Depending on the operating system and version of MDAC... |
| 30466 | When you use ODBC scalar functions with the Microsoft Jet 4.0 OLE DB provider to insert a timestamp that contains a fractional (millisecond) value, the Jet ODBC driver (Odbcjt32.dll) may return the following error message: Return: SQL_ERROR=-1... |
| 30467 | When you run an ADODB command stream and specify SQL SELECT with the FOR XML AUTO clause, an XML document stream is fetched from SQL Server, sent to the response object, and piped to the client. Properties to be set for the properties of the... |
| 30468 | XPath.exe demonstrates how to extract an XML stream from a SQL Server 2000 database by using an XPath query and ADO in Visual C++. |
| 30469 | XMLStream.exe demonstrates how to create an ActiveX Data Objects (ADO) client that uses an SQL XML query to extract an XML stream from a SQL Server 2000 server. |
| 30470 | Hierarchical recordsets can be used as an alternative to JOIN and GROUP BY syntax when you need to access parent-child and summary data. These recordsets can be created by using the SHAPE provider, MSDataShape. Many applications now use a 3-tier... |
| 30471 | When using the SQLOLEDB provider with server side cursors, the error description is not returned from a RAISERROR call inside a SQL Server procedure. An error is raised to the client, however, the description is not returned to the client. Instead the... |
| 30472 | If multiple stored procedures are executed when using ADO 2.0, the T-SQL Debugger automatically starts for the first stored procedure, but does not automatically start upon executing the second or subsequent stored procedures. The following error... |
| 30473 | Identity columns are normally read-only because the server generates the values. However, when you migrate data from one table to another you often want to keep the existing Identity column values rather than use server-generated values. Microsoft SQL... |
| 30474 | If you run an ADODB command stream and specify SQL SELECT with the FOR XML AUTO clause, an XML document stream is fetched from SQL Server and displayed in the Visual Basic Intermediate window. You must set the following properties for the Properties... |
| 30475 | When you update tables in SQL Server 7.0, the AddNew and Update methods of the Microsoft ActiveX Data Objects (ADO) Recordset object ignore the ANSI PADDING OFF setting. These methods do not trim the trailing spaces or blanks, even if the table is... |
| 30476 | In Microsoft Visual Basic ActiveX Data Objects (ADO), when connecting through the SQL Server ODBC Driver, using adFilterConflictingRecords does not filter all the conflicting records as expected. |
| 30477 | After you install Microsoft Data Access Components (MDAC) 2.7 Service Pack 1 (SP1), and you try to open an ADO recordset with a query to SQL Server 2000 by using Microsoft SQL Server OLE DB provider, you might receive the following error message:... |
| 30478 | Microsoft XML (MSXML) 3.0 Service Pack 2 (SP2), or later service pack, installs only in replace mode. This release is also included with Microsoft Windows XP, Microsoft Internet Explorer 6.0, and Microsoft Data Access Components (MDAC) 2.7. Replace... |
| 30479 | The following error occurs when accessing a recordset in an Active Server Pages (ASP) file that contains Text or Blob type data from a SQL table: Microsoft OLE DB Provider for ODBC Drivers error '80020009' |
| 30480 | When you open a Schema Recordset, such as adSchemaColumns or adSchemaProviderTypes, against Microsoft SQL Server 2000, the BIGINT data type is mapped to adChar (129) instead of adBigInt (20). |
| 30481 | When using the SQL Server ODBC driver with forward-only server-side cursors in trying to access a local temporary SQL Server table that was explicitly created using the same ActiveX Data Object (ADO) connection object, the application receives the... |
| 30482 | When you are trying to execute a query which contains a constraint violation and should return the error message DB_E_ERRORSOCCURED and you call ICommandPrepare-Prepare prior to calling ICommand-Execute , ICommand-Execute returns S_OK . To work... |
| 30483 | When you attach an ActiveX Data Objects (ADO) Recordset to the Microsoft ADO Data Control, the following error message occurs: Run-time error '-2147417848 (80010108)': Method 'Recordset' of object 'IAdodc' failed |
| 30484 | After you update your system to MDAC 2.7 or install Microsoft Windows XP, you cannot update Data Environment recordsets that you retrieve from Microsoft Visual FoxPro databases by using command objects of type Table and you receive the following error... |
| 30485 | When you open an ActiveX Data Objects (ADO) recordset with pessimistic locking on already locked data and then check the recordset for the EOF property, you receive different results on Microsoft SQL Server 6.5, Microsoft SQL Server 7.0, and Microsoft... |
| 30486 | From a client computer that has Microsoft Data Access Components (MDAC) 2.6 and SQL Server ODBC Driver version 2000.80.194, if you try to retrieve all of the server names by calling the SQLBrowseConnect() ODBC API function, you will not receive any... |
| 30487 | The following error may be generated by the Microsoft SQL Server ODBC driver, especially when you are using the ODBC driver in connection-pooled environments such as Internet Information Server (IIS): Error 0x8000FFFF Catastrophic failure The typical... |
| 30488 | Information regarding the versions of Microsoft SQL Server can be useful when you are writing commands that are intended to be specific to a particular version of SQL Server. To check for version information, use one of the following methods: Use the... |
| 30489 | The Remote View designer has only two types of Join conditions, Left Outer and None. |
| 30490 | With the Microsoft OLE DB Provider for SQL Server (SQLOLEDB), when you try to run multiple commands in the same session within the scope of a transaction, you may receive the following error message: Cannot create new connection because in manual or... |
| 30491 | When Microsoft Data Access Components (MDAC) version 2.6 is installed, each attempt to connect to a SQL Server 7.0 or SQL Server 2000 database using an IP address (rather than the server name) may take longer than anticipated. In certain reported... |
| 30492 | This article describes, by example, how to implement a Visual C++ Component Object Model (COM) object that returns a recordset to Active Server Pages (ASP). Implementing this incorrectly can result in memory leaks or one of the following errors: The... |
| 30493 | This article describes, by example, how to implement a Visual Basic Component Object Model (COM) Object that returns a recordset to Active Server Pages (ASP). Implementing this incorrectly can result in memory leaks or one of the following errors: The... |
| 30494 | When you call a Microsoft SQL Server Stored Procedure through ODBC and supply a variable for the return or OUTPUT parameter, a single character variable name causes an error. |
| 30495 | If you persist a Microsoft ActiveX Data Objects (ADO) recordset into an external XML file, and you then load the XML file into an ADO Stream object and open another ADO recordset on the ADO Stream object, the following error messages occurs: Code =... |
| 30496 | If you install Microsoft Data Access Components version 2.6 on an Exchange 2000 server, double-byte character set (DBCS) characters in the subject, location, and body part of a reply of meeting request may not display correctly when you use Microsoft... |
| 30497 | When fetching rowset values into nonvariant datatypes, ActiveX Data Objects (ADO) may suppress errors that are related to the status of the recordset, such as notifications that the record is locked by another user. This problem occurs in Microsoft... |
| 30498 | When you use an ADOX key object collection to retrieve the primary key column information of a Microsoft Access table or SQL Server table, a C++ exception may occur. Microsoft Visual Basic code may return the following error: operation is not... |
| 30499 | Negative values inserted into numeric fields of remote views of SQL Server tables are rounded up by 0.01. |
| 30500 | This article describes how to pass a single quote in a string to a SQL Server table using SQL passthrough with a DSNless ODBC connection. |
| 30501 | After deleting a row and doing a MoveNext or MovePrevious, the current record is wrong. Exhibited behavior indicates that the current record will either become another record from within the recordset or EOF depending on the size of the recordset. |
| 30502 | If you try to back up or restore a database on a computer that is running Windows Server 2003, the process may fail with a General Network Error if the process is connected through named pipes. |
| 30503 | This article describes how to determine the compatibility level of a SQL Server 7.0 Database from Visual FoxPro. |
| 30504 | A call to certain stored procedures that contain parameters may fail, resulting in OLE DB error 0x80004005 when using the Microsoft OLEDB Provider for Oracle older than version 2.10.3912.0. |
| 30506 | This article lists article numbers for bugs that were fixed in Microsoft Data Access Components (MDAC) Service Pack 3 (SP3). |
| 30507 | When Microsoft Data Access Components (MDAC) components are used under extremely low memory conditions, an unhandled access violation (AV) may occur. |
| 30508 | When you use Microsoft ActiveX Data Objects (ADO) to retrieve data, an access violation occurs in Oledb32.dll. |
| 30509 | When you use the NoWorkerThread connection string property with Microsoft OLE DB Provider for Oracle (MSDAORA), worker threads are still spawned when you use the provider with distributed transactions. |
| 30510 | During the Windows Components Update portion of Visual Studio .NET Setup, the Microsoft Data Access Components (MDAC) portion of the update fails with the following error message: digital signature error NOTE : If you are instructed to install MDAC... |
| 30511 | If you install Microsoft Data Access Components (MDAC) version 2.1, 2.5, or 2.6 on Windows NT 4.0 Terminal Server or Windows 2000 Terminal Services, sometimes the MDAC installation may fail. This problem may also occur after you use Component Checker... |
| 30512 | When you use SQL commands that return messages in an asynchronous fashion, such as the Microsoft SQL Server BACKUP ... WITH STATS command, which returns a %Complete message at points in the procedure, the command executes, but the notification... |
| 30513 | After you update the filtered column in an ActiveX Data Objects (ADO) recordset, the row pointer position changes behavior from Microsoft Data Access Components (MDAC) 2.1 to MDAC 2.5 and 2.6. This problem only occurs when you use a server-side keyset... |
| 30514 | Installation of Microsoft Data Access Components (MDAC) 2.6 or later on a computer that is running Windows 2000 may roll back at the very end of the installation process. The Dasetup.log file (located in the Windows directory) shows that verification... |
| 30515 | This article describes the process of using new Visual FoxPro 6.0 tools to create applications with minimal coding required. The new Application Wizard automatically creates a full featured, robust application framework that handles common application... |
| 30516 | This article illustrates how you can use the Visual FoxPro Connection Designer to visually setup an ODBC File (data source name) DSN. |
| 30517 | When opening the ODBC Setup PPC control panel, the following error message is received (usually endlessly): An unexpected error occurred, because an error of type -192 occurred. Or after setting up a data source in the control panel, one or more of... |
| 30518 | When creating a database Stored Procedure in an ODBC Script File window via the ODBC Script File dialog box (from the File menu, select New and click the File tab), the ODBC Script File dialog box does not act like a Stored Procedure Editor dialog... |
| 30519 | This article shows by example how to create remote connections and remote views programmatically. |
| 30520 | Visual FoxPro 6.0 contains the new Foundation Classes (FFC) that offer support for a wide variety of database and application functionality. One of the more important tasks of today's applications is the ability to access the Registry. The FFC... |
| 30521 | If you create a Pivot Table in Microsoft Excel using Visual FoxPro's Pivot Table Wizard and then change the data in the table on which the Pivot table is based, the Excel Pivot Table does not update to reflect the change in the underlying data. |
| 30522 | When you try to connect to a data source on a SQL Server, you may receive an error, which may be intermittent, that is similar to this: [Microsoft][ODBC SQL Server Driver]TDS buffer length too large(#0) |
| 30523 | This article describes how to create a Remote View programmatically in Visual FoxPro to access data that resides in a Microsoft Excel spreadsheet (.xls file). |
| 30524 | You have a remote view to a Visual FoxPro table using the Visual FoxPro ODBC driver. When you attempt to issue a TABLEUPDATE() after replacing a memo field value with an empty string (), the TABLEUPDATE() fails with the following error: Connectivity... |
| 30525 | This article lists various 80004005 error messages, the most frequent causes of the error messages, and troubleshooting steps to resolve them. The 80004005 error is received by Microsoft Data Access Components (MDAC) in Active Server Pages, including... |
| 30526 | The Dasetup.exe program, when used with the /u switch, may not correctly roll back Microsoft Data Access Components (MDAC) to the previous version. You can verify this by using the Component Checker utility which is available at the following... |
| 30527 | When launching Visual InterDev, an error message can occur stating that there is a version conflict between two or more ODBC system files. |
| 30528 | The ATLShape.exe sample demonstrates how to retrieve hierarchical data by using the MSDataShape provider. The sample reads data from either a Microsoft Access 97 database or a SQL Server 7.0 database, and writes it to an Example.out text file. Active... |
| 30529 | Some OLE DB providers, such as Microsoft's Oracle OLE DB Provider, do not support updating via IRowsetChange, although they do support updating via SQL UPDATE statements. In this case, the OLE DB Cursor Engine service can be used to allow the provider... |
| 30530 | When working with parameterized SQL Server stored procedures by using a data access technology such as ActiveX Data Objects (ADO), the members of the Parameters collection of the ADO Command object can be referenced by using either the name of the... |
| 30531 | When you attempt to run simple ActiveX Data Objects (ADO) code in an application, the following error can occur: Method '~' of Object '~' Failed |
| 30532 | Trying to issue an Update or Resync command on a recordset based on a SQL Server view might generate the following error: Run-time error '-2147217911 (80040e09)': SELECT permission denied on object table_name, database db_name, owner owner_name |
| 30533 | When an ADO application is redistributed, it produces the following run-time error on the user's computer: Run-time Error 430 Class does not support automation or does not support expected interface. |
| 30534 | Because Microsoft Excel is such a powerful data analysis tool, Visual Basic and VBA application developers often want to bring data into an Excel worksheet for analysis purposes. This article describes the ActiveX Data Objects (ADO) approach to this... |
| 30535 | When your Visual Basic project references the Microsoft ActiveX Data Objects library, if you use the Package and Deployment Wizard (PDW) to build the installation package, the Package and Deployment Wizard includes the Mdac_typ.exe file to install... |
| 30536 | When a query is run on one thread and canceled on another, the thread that executes the query with SQLExecute() is not notified by the return values that query was canceled. |
| 30537 | When you execute a statement that was prepared with the SQL_ATTR_NOSCAN attribute, you may receive an access violation (AV) as follows: Unhandled exception in appname.exe (SQLSRV32.DLL): 0xC0000005: Access Violation. |
| 30538 | When an application uses connection pooling through ActiveX Data Objects (ADO), OLE DB, or Open Database Connectivity (ODBC), and the following conditions are true The default settings (for example, ANSI padding or warnings behavior) of the DSN used... |
| 30539 | Calling the ODBC API SQLTables() function on a SQL Server database name that contains an underscore (for example, my_db) may not return any of the table names contained in the database. When you use MDAC 2.7 SP1, and you call SQLTables with a... |
| 30540 | When you insert values into a table with an identity column, SQL Server automatically generates the next identifier based on the last used identity value. You might want to retrieve this automatically generated identity value immediately after an... |
| 30541 | To determine what Oracle components are installed on your system (and the version of these components) open either the NT.rgs or WIN95.rgs file. These files are located in the \ORINST directory off the Oracle home directory. |
| 30542 | This article lists the different versions of the ODBC Driver Manager and the SQL Server driver shipped. |
| 30543 | If an application inserts more than 400 kilobytes (KB) of data in SQL Server by using ODBC, you may receive the following error message: DIAG [22026] [Microsoft][ODBC SQL Server Driver]String data, length mismatch (0) You receive this error message if... |
| 30544 | Unsup.exe is a sample that searches a text (.txt) file or program (.prg) file for commands that are not supported by the Visual FoxPro ODBC driver version 1.0. |
| 30545 | Under some circumstances, the SQL Server 2000/MDAC 2.6 RTM version of Microsoft ODBC Driver for SQL Server (2000.80.194) reuses a parameter binding that is too short. This truncates the parameter value and causes incorrect or no data to be returned.... |
| 30546 | When you use Microsoft ODBC Driver for SQL Server to fetch data in asynchronous mode, you may see that the data that is fetched is corrupted for some of the columns. This corruption does not always occur, and is random in nature. Most of the time you... |
| 30547 | When you set or check the default column values for any column in a table that is contained in an Access 2000 database, the default values for the column are cleared. |
| 30548 | When ICommandPrepare::Prepare is called from a Command object on a nonexistent table, it returns an HRESULT of S_OK instead of DB_E_ERRORSINCOMMAND(0x80040E14) or DB_E_NOTABLE (0x80040e37). This behavior occurs with the Jet OLE DB Provider when... |
| 30549 | The Sqlfstin.exe sample demonstrates how to perform quick, transactional inserts of a large number of records into SQL Server by using the IRowsetFastLoad interface and the ATL OLE DB consumer templates. The sample also shows how to roll back such... |
| 30550 | When an ATL OLE DB Oracle client application uses the Microsoft OLE DB Provider for Oracle (MSDAORA), that is included with MDAC 2.7, to retrieve data from an Oracle function by using a REF CURSOR, the application leaks memory each time a command is... |
| 30551 | Web servers and COM+ applications may experience blocking and 100 percent CPU usage when they use OLE DB session pooling. Two significant changes were made to the Microsoft OLE DB session pooling code to help alleviate blocking and the 100 percent CPU... |
| 30552 | Under the following conditions: you are using the Microsoft OLE DB Provider for Oracle to connect to Oracle 8i database -and- you are running a stored procedure inside of a package that returns 50 or more output parameters an Unspecified Error is... |
| 30553 | When you use an ActiveX Data Objects (ADO) server-side cursor with the Microsoft OLE DB Provider for DB2 (DB2OLEDB) that comes with Host Integration Server or with SNA Server 4.0 SP3 or SP4, the following error may occur when you try to update a... |
| 30554 | When an application that uses Microsoft Jet database engine 4.0 is rapidly inserting records into a database file that is in Access 97 format, the application may stop responding, or hang, after some random amount of time and the application has to be... |
| 30555 | When you attempt to connect to an Oracle 8i database by using the Oracle 8i client and the Microsoft Oracle ODBC Driver (MSORCL32.DLL) version 2.573.4403 (or later) or the MS Oracle Provider (MSDAORA.DLL) version 2.50.4403.0 (or later), you may... |
| 30556 | When you attempt to use versions 3.0 or later of the MSXML parser to parse XML documents that contain certain low-order non-printable ASCII characters (that is, characters below ASCII 32), you may receive the following error message: An Invalid... |
| 30557 | If you have an XML string or document you may use it to open an ActiveX Data Objects (ADO) recordset. You can do this by using the Microsoft ADO 2.5 Stream object and the new XML integration features in ADO. This article describes the mechanism... |
| 30559 | This article lists known references you may find helpful when learning ODBC. Books ODBC 3.5 Developers Guide, Sanders, Roger, McGraw-Hill, ISBN: 0-07-058087-1 Teach Yourself ODBC Programming in 21 days, Whiting, Bill; Morgan Bryan; Perkins, Jeff;... |
| 30560 | This article covers some of the Frequently Asked Questions (FAQ) about the SDK for Java. For other Java related FAQs search the Web at: http://msdn.microsoft.com/support for 'JAVA' and 'FAQ'. |
| 30561 | When issuing a query against an Oracle database or calling an Oracle procedure from an Active Server Pages (ASP) application, the following may occur: The service (WWW service) may stop responding to requests for the ASP pages. The service may shut... |
| 30562 | MDAC is a collection of components that provide database connectivity on Windows operating sytems. MDAC is a ubiquitous technology, and it is likely to be present on most Windows systems, including the following: MDAC is included by default as part of... |
| 30563 | This article provides information about the Microsoft Baseline Security Analyzer tool (MBSA). This tool centrally scans Windows-based computers for common security misconfigurations and generates individual security reports for each computer that it... |
| 30564 | If a deadlock condition occurs on Microsoft SQL Server in an application that uses the open database connectivity (ODBC) cursor library, a function call to the ODBC API SQLExtendedFetch returns SQL_SUCCESS instead of SQL_ERROR . This return is... |
| 30565 | When you install Microsoft Data Access Components (MDAC) versions 2.6 or 2.7 on a computer that is running Windows NT 4.0 or Windows 2000, you may receive the following error message: 0x80070057 The parameter is incorrect. The Dasetup.log shows that... |
| 30566 | When you save a large recordset to the Advanced Data Tablegram (ADTG) format by using the Microsoft SQL Server OLE DB Provider (SQLOLEDB) and setting the CursorLocation property to adUseServer , some data may be lost when the recordset is reopened... |
| 30567 | Microsoft COM+ continuously tries to unload OLE DB and succeeds. When OLE DB is unloaded, the session pool and its threads are freed. At the same time, new calls are being made into OLE DB, which causes the DLL to load again and the session pool to be... |
| 30568 | The Microsoft OLE DB Provider for Oracle may leak memory when used to execute a stored procedure against Oracle that returns extra output parameters after a result set. |
| 30569 | If Microsoft Data Access Components (MDAC) 2.6 Service Pack 1 (SP1) is installed immediately after installing MDAC 2.6 RTM, without restarting Windows 2000 between the two MDAC installations, the MDAC 2.6 SP1 installation may fail with the following... |
| 30570 | After you install Microsoft Data Access Components (MDAC) version 2.6 or 2.6 Service Pack 1 (SP1), the ODBC Driver for Visual FoxPro no longer supports the adAsyncExecute flag. When you try to use this flag from ActiveX Data Objects (ADO), you receive... |
| 30571 | In some applications, if you use Microsoft Jet databases that contain tables that are linked to external data sources through ODBC, you may want to provide the logon name and password of the current user at run time to connect to the remote data... |
| 30572 | When you attempt to execute a SELECT statement with parameters by using the ODBC driver for SQL Server 2000 that is included in Microsoft Data Access Components (MDAC) version 2.6 Service Pack 1 (SP1) or Service Pack 2 (SP2), you may receive an error... |
| 30573 | This article provides information about the bugs fixed by Microsoft Data Access Components (MDAC) 2.6 service packs. Because service packs are cumulative, subsequent service packs also fix the bugs fixed by earlier service packs. For example, MDAC 2.6... |
| 30574 | Service packs are the means by which Microsoft Data Access Components (MDAC) bug fixes are distributed. Service packs keep the product current. Service packs may include updates, system administration tools, drivers, and additional components. All are... |
| 30575 | If you use the SQLConfigDataSource ODBC API call with the REPAIR_DB option on an encrypted Microsoft Access database file, the database is properly repaired, but the encryption is removed. |
| 30576 | When you insert a number of records into a table in a Microsoft Access database, you may want any records that duplicate existing records to be ignored with no error or warning message, and you may want only unique new values to be inserted. Data... |
| 30577 | The Microsoft ODBC Driver for Access leaks handles and threads upon opening and closing the connection. This problem is observed in drivers that ship with MDAC 2.5, 2.5 SP1, and Jet 4.0 SP5. |
| 30578 | When you use the Microsoft Oracle OLE DB Provider (MSDAORA) to open an ADO Recordset on a SELECT statement that contains a UNION in a sub-select query, you may receive the following error message: Unspecified Error |
| 30579 | After you upgrade Microsoft Data Access Components (MDAC) to a later version, custom registry settings for the MSDASQL OLEDB provider may be lost. This can cause problems on systems on which these default settings have been changed to avoid certain... |
| 30580 | When you use the Microsoft Excel Open Database Connectivity (ODBC) Driver to connect to an Excel worksheet as an ODBC data source, the driver assumes by default that the first row of worksheet data contains column headers (field names). According to... |
| 30581 | With the Microsoft OLE DB Provider for Oracle (MSDAORA), the execution of a SQL statement that contains both an IN and a UNION clause may produce an ActiveX Data Objects (ADO) Recordset object that contains an incorrect number of columns. This problem... |
| 30582 | With the Microsoft OLE DB provider for SQL Server (SQLOLEDB), if you try to access a database on a remote SQL Server that doesn't exist on a local SQL Server, the following error may occur: Cannot open database requested in login 'database name'.... |
| 30583 | When inserting records into a Microsoft Access database, immediately attempting to reselect them occasionally does not return all inserted records. This occurs even when the records are inserted and reselected on the same connection. The problem... |
| 30584 | With the SQLOLEDB provider that ships with MDAC version 2.5 or 2.5 SP1, calling a Microsoft SQL Server stored procedure with one or more PRINT statements that return more than 512 bytes of data each may result in an access violation. The error message... |
| 30585 | The Microsoft OLE DB Provider for ODBC Drivers method IDBSchemaRowset::GetRowSet() fails with DB_E_ERRORSOCCURRED when an ODBC driver returns a TABLE_TYPE string of more than 15 characters. The specific error is: Run-time Error '-2147217887... |
| 30586 | An access violation occurs when you call a SQL Server stored procedure that contains a PRINT statement that displays a string containing approximately 700 characters. This occurs with the Microsoft OLE DB Provider for SQL Server (SQLOLEDB). |
| 30587 | This article demonstrates the use of Microsoft ActiveX Data Objects Extensions for Data Definition Language and Security (ADOX) to access different groups, properties, and the new TRUSTEE PIN property that is introduced in MDAC 2.6. |
| 30588 | Active Template Library (ATL) OLE DB Consumer libraries provide four types of accessors template classes to retrieve or manipulate data. ATL4Acc.exe is a sample that demonstrates data retrieval from a Microsoft SQL Server version 7 stored procedure... |
| 30589 | The Microsoft OLE DB Provider for Jet version 4.0 is installed by Microsoft Data Access Components (MDAC) versions 2.1 and 2.5 which are in turn installed by various applications. In several areas, Jet 4.0 provides additional features and better... |
| 30590 | The Update Resync dynamic property cannot be persisted properly when the Recordset object is saved in Extensible Markup Language (XML) format in releases of Microsoft Data Access Components (MDAC) prior to 2.5. It only works when the recordset is... |
| 30591 | When you try to open a record object with a URL specified as the active connection, you might get the following error: Run-time error '-2147467259 (80004005)': [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified. |
| 30592 | In certain cases, you may want to determine if a Primary Key is defined on an underlying database table and if so, what columns are used in that Primary Key. You can obtain this information by using Microsoft ActiveX Data Objects Extensions for Data... |
| 30593 | When upsizing a table containing a currency field to SQL Server 7.0, it could return the error: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]Implicit conversion from data type char to money is not allowed. Use the CONVERT... |
| 30594 | Mtxoci.dll is a dynamic-link library (DLL) that is used internally by the Microsoft ODBC Driver for Oracle and the Microsoft OLEDB Provider for Oracle in conjunction with Microsoft Distributed Transaction Coordinator (DTC) to provide transactional... |
| 30595 | When attempting to issue a SQLSetPos () (UPDATE a record) on a SELECT statement that uses table names in the field/column list, you will receive the following error message: [Microsoft][ODBC driver for Oracle]Degree of derived table does not match... |
| 30596 | When you are using Microsoft OLE DB provider for Oracle (Msdaora.dll), a SELECT statement containing the DISTINCT keyword causes the BASECOLUMNNAME property of the first field in the recordset to be named DISTINCT instead of its real name. If you... |
| 30597 | A client application may receive the following error when using Msorcl32.dll version 2.5 (build 2.573.2927, 2.573.3513, and 2.573.4403): [Microsoft][ODBC Driver for Oracle]Error in column #: Numeric value out of range. |
| 30598 | When you call an Oracle package.procedure that does not take any parameters the Microsoft Oracle ODBC driver returns the following error message: SYNTAX ERROR OR ACCESS VIOLATION |
| 30599 | Service Pack 5a for SQL Server 6.5 provides an optional installer for Microsoft Data Access Components 2.1 (MDAC 2.1). |
| 30600 | This article lists various versions of MDAC, the Microsoft SQL Server ODBC driver, ODBC driver manager, Jet driver and Jet engine versions shipped with each of them, platforms supported and the major products that ship them. |
| 30601 | This article demonstrates how to programmatically use Data Links feature of the Microsoft Data Access Components in order to generate a connection string at run-time. |
| 30602 | After upsizing a database that had primary key indexes in two tables with the same field and or tag name, the following error occurs: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]There is already an object named 'f1' in the... |
| 30603 | Microsoft OLE DB Provider for Index Server (MSIDXS) supports the Data Source property to specify a Catalog name when querying the contents of Index Server. |
| 30604 | When you attempt to create an ODBC data source with the SQLConfigDatasource API and the Microsoft ODBC Driver for Oracle version 1.0 (Msorcl10.dll), you get one of error messages listed below. On Windows 95: APPLICATION.EXE has caused an invalid... |
| 30605 | Opening the connection on a read-only Microsoft Access Database (.mdb file on a CD-ROM, a floppy disk that is write protected, or a hard disk that is read-only to the user, and so forth) with the following code causes an error to occur. The following... |
| 30606 | Microsoft Data Access Components (MDAC) version 2. x has increased inter-dependencies compared to previous releases. This poses some implications for redistribution, especially for Remote Data Service (RDS) Client applications. |
| 30607 | When trying to run or browse a remote view, you may receive a Connectivity error similar to this one: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]'CTOD' is not a recognized built-in function name |
| 30608 | When using the Setup Wizard in Microsoft Visual FoxPro 3.0b, if you select the Btrieve Driver alone in the ODBC Drivers dialog box, the error Required File Missing: MSJINT32.DL_ will occur. The error message appears after the Finish button is... |
| 30609 | When using the 16-bit Oracle 7 ODBC driver (Sqora7.dll version 1.11.0000) that ships with Visual FoxPro to connect to an Oracle 7 server, the connection fails with the following error message: Connectivity Error [Microsoft][ODBC DLL] Driver's... |
| 30610 | Neither Open Database Connectivity (ODBC), nor Microsoft OLE DB Provider, supports Nested Transactions. ActiveX Data Objects (ADO) supports the feature, but only if the underlying provider exposes it. Currently only the Jet OLE DB provider supports... |
| 30611 | When connecting through SQL Server Driver that comes with Microsoft Data Access Components (MDAC), the ODBC Client may receive the following (or a similar) error message after connecting successfully: The ODBC catalog stored procedures installed on... |
| 30612 | On a computer with the original release of Windows 95 (version 4.00.950), if you run the Microsoft Data Access Components (MDAC) standalone setup program, the dialog box for the setup program appears 10-20 times wider than the screen. If you slide the... |
| 30613 | If you use Microsoft ODBC Driver for SQL Server 2000, and the ODBC API SQLDesribeParam function is used to describe the parameter marker of a query that involves an outer join, you receive the following error messages: [Microsoft][ODBC SQL Server... |
| 30614 | If you connect from a client to your SQL Server using either the Microsoft ODBC Driver for SQL Server, the Microsoft OLE DB Provider for SQL Server, or the System.Data.SqlClient managed provider, and you keep your connection idle for about 30 seconds,... |
| 30615 | This article lists the locations of the available release manifests for Microsoft Data Access Components (MDAC) products. |
| 30616 | The following error may occur when calling Open() for a CDatabase or CRecordset object: General error: Unable to create file buffer. State:S1000,Native:0,Origin:[Microsoft][ODBC Cursor Library] -or- General error: Unable to write to file buffer... |
| 30617 | Documents that ship with the Professional Edition of Microsoft Visual FoxPro version 3.0 for Windows and the Visual FoxPro Help file incorrectly list the ConnectName property as being available with the SQLGETPROP() function. However, using the... |
| 30618 | A connection to a back-end SQL Server database may fail, and you receive the following error message: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()). [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not... |
| 30619 | When you use the Microsoft SQL Server driver that is included with Microsoft Data Access Components (MDAC) version 2.6 or 2.7, if you call the SQLDescribeParam function on a connection that is busy with results for another statement handle,... |
| 30620 | Sometimes client computers that are running Microsoft Windows 98 Second Edition (SE), and that use MDAC 2.7, cannot connect to a named instance if Microsoft SQL Server 2000. Instead, they may receive the following connection error message: [TCP/IP... |
| 30621 | The Server drop-down list may be empty even if you have Microsoft SQL Server (for example, version 7.0 or version 6.5) installed on your network. The Server drop-down list is empty if the following conditions are met: You have clicked Microsoft OLEDB... |
| 30622 | When Analysis Services 2000 is installed on a system that has Microsoft Visual Studio .NET Beta 2 installed, the following error may be seen when attempting to drill down on a member in the cube browser: (Unable to retrieve children: Member with the... |
| 30623 | When you are using Microsoft Data Access Components (MDAC) version 2.6 from a client application to connect to a SQL Server 7.0 database, the client application may start to experience login timeouts, Timeout expired errors, or general network... |
| 30624 | Service packs are the means by which Microsoft distributes bug fixes. Service packs keep a product current. Service packs include updates and may include system administration tools, drivers, and additional components, which are conveniently bundled... |
| 30625 | Windows XP is shipped with Microsoft Data Access Components (MDAC) 2.7 as a part of the operating system. Because of this, the MDAC 2.7 redistributable installer, Mdac_typ.exe, has no effect on the MDAC installation on Windows XP computers. |
| 30626 | When you call the OLEDBSimpleProviderListener::aboutToChangeCell or OLEDBSimpleProviderListener::cellChanged method, Microsoft OLE DB Simple Provider (OSP or MSDAOSP.dll) does not issue notifications. |
| 30627 | After you install Microsoft Data Access Components version 2.6, queries that use the Active Directory Services Interfaces (ADSI) OLEDB provider, ADSDSOObject, may return the following error: Error -2147221164 (80040154) : Class not registered |
| 30628 | When you use Microsoft Data Access Components (MDAC) 2.5, calling the SQLParamData function with a static server-side cursor returns SQL_ERROR (-1), and you may see this error message: [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect... |
| 30629 | When running a stored procedure with the SQL Server ODBC driver that ships with Microsoft Data Access Components (MDAC) version 2.6, you may receive the following error message: [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax... |
| 30630 | If you turn off OLE DB session pooling and run the Visual Basic Bank sample program three times in succession, you receive the following error message on the third iteration: -2147217900 [Microsoft][ODBC SQL Server Driver][SQL Server]Distributed... |
| 30631 | In some cases, when running queries from Microsoft Access or any application that uses Jet/VBA, like Data Access Objects (DAO), that involve an ODBC timestamp or SQL datetime data with the fractional portion of the timestamp having a higher precision... |
| 30632 | The Microsoft Data Access Components (MDAC) 2.1 or later version of the Microsoft OLE DB Provider for SQL Server may not store some ASCII and extended characters correctly if the code page for SQL Server does not match the client's code page. Instead,... |
| 30633 | Oracle number fields with a precision greater than 9 and with a scale of 0 are defined as type Text when they are linked into a Microsoft Access 97 database programmatically through Microsoft ActiveX Data Objects Extensions for Data Definition... |
| 30634 | When ODBC connection pooling is enabled, if database servers are down or unavailable due to network connectivity issues, Internet Information Server (IIS) or Microsoft Transaction Server (MTS) may stop responding (hang). |
| 30635 | After you install Microsoft Data Access Components (MDAC) version 2.6, and you try to copy and paste an OLAP object from OLAP Manager or use the Cube/Dimension Editor to add a new object, you may receive the following error message: Arguments are of... |
| 30636 | When using the Advworks data source name (DSN) that installs with the Microsoft Data Access Components (MDAC) files, the following error may occur: Run-time error -2147467259(80004005) General Error Unable to Open registry key DriverID. |
| 30637 | This article deals with redistribution of Microsoft Data Access Components (MDAC), which includes ODBC, OLE DB, ADO, RDS, the MDAC Standalone, MDAC Redistribution and the Data Access SDK. |
| 30638 | When you attempt to create a Data Source Name (DSN) for the Alpha version of the Microsoft Oracle ODBC Driver (v2.573.2927) for use with the Oracle8 client components, you receive the following error: The Oracle(tm) client and networking components... |
| 30639 | The Microsoft Access ODBC Driver does not support multiple result sets of native Access tables. Calling SQLGetInfo( hdbc, SQL_MULT_RESULT_SET, ... ) returns an 'N' signifying the driver does not support multiple result sets. This means an application... |
| 30640 | When inserting data into a Bit (Yes/No) field in a Microsoft Access database via the Microsoft Access ODBC driver, the resulting data in the bit field is always False, even when a value of True was specified. This behavior occurs when using the... |
| 30641 | When Microsoft Internet Explorer displays a Web page that uses Remote Data Services (RDS), an access violation may occur in Internet Explorer, and you may receive the following error message: Microsoft Internet Explorer has encountered a problem and... |
| 30642 | This article provides information about the bugs that are fixed with the Microsoft Data Access Components version 2.7 Service Pack 1 (MDAC 2.7 SP1). To download MDAC 2.7 SP1, visit the following Microsoft Web site:... |
| 30643 | This article lists the significant changes in Microsoft Data Access Components (MDAC) version 2.8 from the previous versions of MDAC. This information includes references to the online documentation, relevant Microsoft Knowledge Base articles, and... |
| 30644 | When attempting to establish a connection to a remote data source using a connection created with the Connection Designer, Visual FoxPro fails, and displays this error message: Connectivity error: [Microsoft][ODBC DLL]Data Source Name Too Long |
| 30645 | You may see a memory leak when repeatedly loading and unloading the Microsoft OLE DB provider for SQL Server (SQLOLEDB) and connecting to a Microsoft SQL Server database. You may see the same behavior when using the Microsoft OLE DB provider for ODBC... |
| 30646 | If you try to save a Project 98 project to an Oracle database using an ODBC data source name (DSN) and the Microsoft ODBC for Oracle driver on a computer that is running the German or the Japanese version of Microsoft Windows 2000, you receive the... |
| 30647 | MDAC 2.6 sp2 is a service release to MDAC 2.6 that originally was included with Microsoft SQL Server 2000 Service Pack 2. The MDAC 2.6 sp2 Refresh is an MDAC release available as a stand-alone download from the following Microsoft Web site: MDAC... |
| 30648 | If the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion registry key contains a registry value that is larger than 255 characters, the Microsoft Data Access Components (MDAC) Component Checker may not be able to find the files in the... |
| 30649 | Rollback of the Microsoft Data Access Components (MDAC) 2.6 Service Pack 2 (SP2) Refresh may fail under the following circumstances: Install of Microsoft SQL Server 2000 SP2 Install of MDAC 2.6 SP2 Refresh Release Rollback of MDAC by running dasetup... |
| 30650 | When you install Microsoft Data Access Components (MDAC) version 2.6 or later on a computer that is running Microsoft Windows 2000 or Microsoft Windows XP, either the installation program completes but does not actually install MDAC, or it displays a... |
| 30651 | This article discusses the version of Microsoft Data Access Components (MDAC) that is installed with Microsoft Windows 2000 Service Pack 4 (SP4). |
| 30652 | A recordset may lose synchronization in Microsoft Internet Explorer if both of the following conditions are true: You pass back an empty Microsoft ActiveX Data Objects (ADO) Recordset object to Microsoft Internet Explorer by using the Remote Data... |
| 30653 | This article requires a good knowledge of Component Object Model (COM), Microsoft Transaction Server (MTS), and any language to build COM components like Microsoft Visual Basic or Visual C. Multiple connections accrue on a SQL Server database or other... |
| 30654 | Installing Microsoft Data Access Components MDAC 2.6 RTM on Windows 2000 or Windows NT 4.0 Professional, Server, or Advanced Server-based computers prevents error text description from being returned from the Microsoft OLE DB Provider for SQL Server... |
| 30655 | Starting with Microsoft Data Access Components (MDAC) version 2.6, MDAC no longer contains Jet components. In other words, MDAC versions 2.6 and later do not include Microsoft Jet, Microsoft Jet OLE DB Provider, and the ODBC Desktop Database Drivers. |
| 30656 | The most recent version of the Microsoft ODBC driver for Visual FoxPro (VFP) is build 6.1.8629.1. The VFP ODBC driver is no longer included in Microsoft Data Access Components (MDAC) 2.6 or later. |
| 30657 | The Oledbospxml.exe sample demonstrates how to retrieve hierarchical OLE DB rowsets from an arbitrary XML document using the the Microsoft OLE DB Simple Provider (MSDAOSP) that ships with Microsoft Data Access Components (MDAC) version 2.6. |
| 30658 | When you pass an ODBC canonical date literal as a parameter to a SQL Server stored procedure using the Microsoft SQL Server ODBC driver, a syntax error may be reported: [Microsoft][ODBC SQL Server Driver]Invalid time format |
| 30659 | When you install any software that tries to change the ODBC configuration or install ODBC components, such as Microsoft Data Access Components, service packs, or Microsoft Access, or you configure an ODBC data source through the ODBC Administrator,... |
| 30660 | When the Microsoft Access ODBC Driver reads a date prior to 1753, the returned date is not consistent with the date actually stored in the database. When you use the Microsoft Access ODBC Driver to write dates prior to 1753, the stored dates when... |
| 30661 | If you submit a LEFT OUTER JOIN query to the Microsoft Access ODBC driver and a Boolean (Yes/No) column is one of the columns in the fields list, the following error message occurs when you reference the resulting Microsoft ActiveX Data Objects... |
| 30662 | Microsoft Data Link files provide an easy way to create or validate a Microsoft ActiveX Data Objects (ADO) connection string that uses an ODBC Driver or an OLE DB Provider to connect to a given data source. This articles discusses how to use the... |
| 30663 | When using Microsoft SQL 6.5 and MSDASQL provider with multiple ADO client-side recordsets sharing the same connection, and using a Substring on a column, the following error may appear: [Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream.... |
| 30664 | Microsoft Data Links, provided with the Microsoft Data Access Components 2.0, provide a convenient and standard way to create and validate the connection string syntax used with an ODBC Driver or OLE DB Provider. Even if you do not reference the data... |
| 30665 | While you run setup on a computer that has Microsoft Windows version 3.x (16-bit Windows) installed from image disks created using the Microsoft Visual FoxPro Setup Wizard, the following error appears: Setup Parse Error in Initialize pass Object ID... |
| 30666 | The How to Install MDAC with a Windows Installer Merge Module white paper describes how to create a Microsoft Windows Installer merge module for Microsoft Data Access Components (MDAC). This white paper includes a sample merge module that you can... |
| 30667 | When you use the Microsoft Oracle OLE DB Provider (MSDAORA) for Microsoft Data Access Components (MDAC) 2.6 and 2.7 to access an Oracle fixed-length CONSTANT CHAR field, you may find that the length of the string retrieved is far greater than... |
| 30668 | The Microsoft OLE DB provider for SQL Server (SQLOLEDB) is almost ten times slower than the Microsoft OLE DB provider for ODBC Drivers (MSDASQL) when inserting binary large object (BLOB) data into a SQL Server database using a stored procedure. |
| 30669 | For your Microsoft ActiveX Data Objects (ADO), ODBC, OLE DB or Remote Data Services (RDS) applications to work properly you must distribute Microsoft Data Access Components (MDAC) with your application. This article discusses Microsoft Data Access... |
| 30670 | Using the Microsoft Access ODBC driver, you can repair or compact a Microsoft Access database. This functionality is accessable from the ODBC Control Panel, through the ODBC Microsoft Access Setup dialog box. This repair and compact functionality... |
| 30671 | The Microsoft OLE DB SDK contains the Microsoft OLE DB Simple Provider (Msdaosp.dll) file. When you try to set a column of a simple provider by binding with type DBTYPE_STR and calling IRowsetChange::SetData() or IRowsetChange::InsertRow(), the column... |
| 30672 | When submitting changes using the SubmitChanges of the RDS.DataControl or the RDSServer.DataFactory the user may see the following error message: [Microsoft][ODBC Microsoft Access 97 Driver] The Microsoft Jet database engine cannot open the file... |
| 30673 | This article provides a list of some useful articles pertaining to Microsoft Data Access Components (MDAC). MDAC articles are not limited to this list; for a comprehensive list, search the Microsoft Knowledge Base at http://support.microsoft.com with... |
| 30674 | Applications that require the Sybase SQL Server Database Management System and Microsoft Internet Information Server (IIS) version 4.0 or Microsoft Transaction Server (MTS) version 2.0 should use the Connect ODBC for Sybase Driver version 3.5 from... |
| 30675 | With the Microsoft Jet 4.0 ODBC driver, a call to the SQLBulkOperations ODBC function, when preceded by a call to SQLExtendedFetch , may result in the following error: DIAG [S1010] [Microsoft][ODBC Driver Manager] Function sequence error (0) |
| 30676 | Microsoft Data Access Components (MDAC) is a collection of components that is used to provide database connectivity on Microsoft Windows operating systems. MDAC is a ubiquitous technology, and it is likely to be present on most Windows systems. By... |
| 30677 | After the release of this bulletin, it was determined that the vulnerability that is addressed is not with the OpenRowSet command. The OpenRowSet command is a Microsoft SQL Server command. Instead, the vulnerability is with the underlying MDAC... |
| 30678 | Xslatezp.exe is a self-extracting executable that performs data translations between Microsoft Access, Microsoft FoxPro, Microsoft SQL Server, and Microsoft Excel. This article demonstrates translation of data from one database format to another using... |
| 30679 | If you try to open a Microsoft Excel 4.0 file, the ODBC Microsoft Jet driver may return the following error message: [Microsoft][ODBC Excel Driver] The Microsoft Jet database engine could not find the object 'ODBCTest.xls'. Make sure the object exists... |
| 30680 | When you use Microsoft Internet Explorer to open an XML file that has no encoding specified and that contains characters with high ASCII-codes, and your computer is running Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium... |
| 30681 | In the Remote View Wizard, after selecting Microsoft Excel as your data source and subsequently choosing a Microsoft Excel spreadsheet, you receive this error message: Error connecting Excel Files |
| 30682 | Session Summary Thursday, June 19, 2003 This Microsoft Support WebCast provides an overview of the main security features that are introduced in Microsoft Data Access Components (MDAC) 2.8. This is a Level 300 session that will be presented by Ammar... |
| 30683 | Session Summary This session provides an overview of the new features in Microsoft Data Access Components (MDAC) 2.6. Additionally, we will discuss, among other things, how the various MDAC components have been enhanced to incorporate XML. We will... |
| 30684 | When using in-line comments the Microsoft ODBC for Oracle driver may fail with the following error message: Syntax Error or Access Violation. |
| 30685 | If you use the Microsoft Access (Jet) ODBC driver (Odbcjt32.dll version 4.0.5303.1), which is shipped with Microsoft Windows 2000 Service Pack (SP) 1, when you run statements that contain computed columns of a text data type, a call to the... |
| 30686 | Session Summary During this session, we will discuss the differences between ODBC Connection Pooling and OLEDB Session Pooling. We will also talk about different ways to implement pooling from different programming models. This is a Level 200 session... |
| 30687 | This article outlines the different Microsoft Data Access Component (MDAC) versions available and the products that install them. |
| 30688 | This article describes the limitations of the current version of Microsoft ODBC Driver and OLE DB Provider for Oracle. |
| 30689 | When you use a client-side cursor against an Oracle database with the Microsoft ODBC Driver for Oracle, a deferred update is not successful and you receive the following error message: 0x80004005 (Insufficient base table information for updating or... |
| 30690 | When connecting with an ODBC connection (with or without a data source name) using the Microsoft ODBC driver for Oracle, if the specified Transparent Network Substrate (TNS) name does not exist for the Oracle server, an application may receive an... |
| 30691 | This article lists the version numbers of the Microsoft XML parser (Msxml.dll Msxml2.dll, Msxml3.dll, and Msxml4.dll) and the Microsoft products that include this component. |
| 30692 | When you try to create a data source name (DSN) with the Microsoft Text Driver on a computer that has MDAC 2.1 or later installed, you may get the following error: Failed to save table attributes of (null) into (null). |
| 30693 | Session Summary February 10, 2003 In this session, we will discuss three areas related to Microsoft Data Access Components. The categories covered will be General Background Information, Tools and Special Considerations, and Installation... |
| 30694 | Certain tools, such as the SQL Server Enterprise Manager, may not display the Microsoft OLE DB Provider for OLAP Services and Microsoft OLE DB Provider for OLAP Services 8.0 in the list of providers after you upgrade to Microsoft Data Access... |
| 30695 | The Adomd.exe self-extracting executable illustrates how to retrieve actions, functions and sets OLAP schema rowsets from the Microsoft OLE DB Provider for OLAP Services (MSOLAP) that is included with Microsoft Data Access Components (MDAC) 2.6. These... |
| 30696 | If a Microsoft Excel spreadsheet's cells contain formulas, the Import function in Visual FoxPro will not import the data correctly. All or part of the data may be invalid when it is imported to the .dbf file. |
| 30697 | If you apply Microsoft Data Access Components (MDAC) version 2.6 to a computer that is running Windows NT 4.0 Microsoft Message Queue Server (MSMQ), you may receive c00e0013 errors with the following text: 'No connection with sites controller' |
| 30698 | When you call managed or unmanaged transactional COM+ components from ASP.NET, one or more of the following problems may occur in your application: Access violations Memory leaks Handle leaks Deadlocks Poor performance |
| 30699 | When you use transactional Microsoft Transaction Server (MTS)/COM+ components against Oracle databases, the components fail with the following errors in the event log: Event Source: MSDTC Event Category: XATM Event ID: 53286 Date: 10/2/2000 Time:... |
| 30700 | When you open an ActiveX Data Objects (ADO) connection from a transactional component in COM+, Microsoft Transaction Server (MTS), or any transactional Active Server Pages (ASP) page, you may receive the following error message if you use Microsoft... |
| 30701 | When transactional COM+/MTS components call Oracle external stored procedures, no rows are returned the first time, and the following error is returned on subsequent method calls: -2147467259 Microsoft OLE DB Provider for ODBC Drivers[Microsoft][ODBC... |
| 30702 | This article demonstrates how to load a ComboBox with records that are retrieved from a database. This example creates an Active Server Pages (ASP) page that connects to the Adventure Works database. |
| 30703 | When you try to load secure Active Server Pages (ASP files) that use Session or Application objects defined in a secure ASP Application file (Global.asa), it may fail. For example, when you try to load a page that uses a DSN string stored in the... |
| 30704 | When you create your own ActiveX Server components running under Internet Information Server (Inetinfo.exe) for Active Server Pages (ASP) or Remote Data Service (RDS), you may get the following error message when you try to recompile or overwrite your... |
| 30705 | Using Active Server Pages (ASP), you can view images stored in BLOB (Binary Large Object) fields in your Internet browser. This article provides information on how to display a GIF image stored in the Microsoft SQL Server sample database table... |
| 30706 | When you try to open a connection to a Microsoft SQL Server database from an Active Server Pages (ASP) page, you get the following error: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server... |
| 30707 | This article describes the ActiveX Data Objects (ADO) SHAPE command syntax that produces hierarchical recordsets and explains how to traverse hierarchical recordsets. This article also provides sample code. You can use hierarchical recordsets as an... |
| 30708 | This article describes the ActiveX Data Objects (ADO) SHAPE command syntax that produces hierarchical recordsets and explains how to traverse hierarchical recordsets. Sample code is also provided. You can use hierarchical recordsets as an alternative... |
| 30709 | An attempt to update a large (64K or greater) memo field in a client-side recordset using the Jet 3.51 OLE DB provider results in one of the following errors: Errors occurred. Run-time error '-2147217887(80040e21)': -or- Run-time error... |
| 30710 | This article demonstrates how to query and update information in an Excel spreadsheet using ActiveX Data Objects (ADO) from an Active Server Pages (ASP) page. The article also describes the limitations that are associated with this type of... |
| 30711 | Ssadovb.exe is a sample file that demonstrates how to use an ActiveX Data Objects (ADO) Recordset with the OLE DB Provider for Site Server (MSSearchSQL) in a Visual Basic application to query Web site data. |
| 30712 | There are several techniques for returning data in a disconnected recordset using the Remote Data Service (RDS). There are two objects on the client, the RDS.DataControl and RDS.DataSpace, and one object on a server, RDSServer.DataFactory, which you... |
| 30713 | The Idxadovb.exe sample demonstrates how to use an ActiveX Data Objects (ADO) recordset with the OLE DB Provider for Index Server (MSIDXS) in a Visual Basic application to query Index Server 2.0. |
| 30714 | This article provides the ASP code necessary to programmatically determine the parameter requirements for any stored procedure. The sample code provided determines the parameter name, data type, direction, and size of all parameters in a stored... |
| 30715 | When the Microsoft OLEDB Provider for ODBC driver (MSDASQL) is using an ODBC driver that is ODBC 2.x compliant, and the driver reports a SQL_BIGINT datatype (-5), the ODBC provider (MSDASQL) chooses a C datatype of SQL_C_SBIGINT for use in the... |
| 30716 | The Microsoft OLE DB Provider for Internet Publishing allows you to open folders and documents into ADO records and ADO recordsets. An ADO record object can represent a row in a recordset, or a single document or folder opened directly. An ADO stream... |
| 30717 | This article describes the features and the limitations of the current version of the Microsoft .NET Managed Provider for Oracle. |
| 30718 | When you use ASP.Net to retrieve data from Microsoft SQL Server, the Web server may acquire an accumulation of aspnet_wp processes that are not using the CPU and that have only a few remaining threads. During ASP.NET process recycling, an aspnet_wp... |
| 30719 | ADOX.exe demonstrates the use of the Jet OLEDB:Trustee PIN property with the User and Group ADOX objects. These properties are only available when using the Microsoft Jet 4.0 OLE DB Provider. |
| 30720 | If a WITH statement is used to store an empty string value to one field and an uninitialized string to the very next field, an error will occur when using the Microsoft OLE DB Provider for Jet 3.51 or 4.00 that shipped with MDAC versions prior to 2.5.... |
| 30721 | When you install the Microsoft Data Access Components (MDAC) on a system running Windows NT, if you are logged on as a user without Administrator privileges, you see an error such as the following: You must have administrative privileges to install or... |
| 30722 | On a Web server that is using Microsoft Data Access Components (MDAC) 2.5 or 2.6, a memory leak may occur when using ODBC to connect to a data source. You can confirm this by using Performance Monitor to track the private bytes allocated by either the... |
| 30723 | When you use the System.Data.SqlClient.SqlConnection class to connect to a Microsoft SQL Server database with protocol encryption enabled, one or more objects in the .NET-managed heap can be corrupted. This causes the Microsoft .NET application to... |
| 30724 | When you bind a varchar2 type output parameter of an Oracle stored procedure to adBSTR in a Microsoft ADO application, the value that Microsoft OLE DB provider for Oracle (MSDAORA) returns is incorrect. In a Microsoft Visual Basic application the... |
| 30725 | The Ospxml.exe sample demonstrates how to retrieve hierarchical ActiveX Data Objects (ADO) recordsets from an arbitrary XML document using the Microsoft OLE DB Simple Provider (MSDAOSP) that ships with Microsoft Data Access Components (MDAC) version... |
| 30726 | If you try to use Properties in a SQL statement with an out-of-process ADODB component, the Microsoft OLAP provider results in one of the following error messages: (-2147467259) The data provider or other service returned an E_FAIL status. -or-... |
| 30727 | If you try to gain access to an Access 2000 or Access 2002 database, you may receive one of the following errors within your Visual Basic program. If you are using Microsoft ActiveX Data Objects (ADO) (or the ADO Data Control), you receive the... |
| 30728 | When you update linked ODBC tables in a Microsoft Access database, an access violation occurs with the following message: The instruction at '0x1b01a333' referenced memory at '0x0000000c'. The memory could not be 'read'. This error message occurs when... |
| 30729 | When you add a new record to a grouped data access page, the page unexpectedly closes. You receive no error message or warning message. The page simply disappears, and then either Microsoft Access or Microsoft Internet Explorer also quits, depending... |
| 30730 | Using Microsoft Jet version 4.0, sorting is different than in previous versions. For example, assume you have the following records in an Access table: FIELD1 W W- WB W-B In previous versions of the Jet database engine, issuing SELECT * FROM Table1... |
| 30731 | The Update Resync dynamic property cannot be persisted properly when the Recordset object is saved in Extensible Markup Language (XML) format in releases of Microsoft Data Access Components (MDAC) prior to 2.5. It only works when the recordset is... |
| 30732 | The Microsoft OLE DB Provider for ODBC Drivers method IDBSchemaRowset::GetRowSet() fails with DB_E_ERRORSOCCURRED when an ODBC driver returns a TABLE_TYPE string of more than 15 characters. The specific error is: Run-time Error '-2147217887... |
| 30733 | When you use Microsoft Data Access Components (MDAC) 2.5, calling the SQLParamData function with a static server-side cursor returns SQL_ERROR (-1), and you may see this error message: [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect... |
| 30734 | If you submit a LEFT OUTER JOIN query to the Microsoft Access ODBC driver and a Boolean (Yes/No) column is one of the columns in the fields list, the following error message occurs when you reference the resulting Microsoft ActiveX Data Objects... |
| 30735 | Microsoft OLE DB Provider for Index Server (MSIDXS) supports the Data Source property to specify a Catalog name when querying the contents of Index Server. |
| 30736 | Opening the connection on a read-only Microsoft Access Database (.mdb file on a CD-ROM, a floppy disk that is write protected, or a hard disk that is read-only to the user, and so forth) with the following code causes an error to occur. The following... |
| 30737 | When trying to run or browse a remote view, you may receive a Connectivity error similar to this one: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]'CTOD' is not a recognized built-in function name |
| 30738 | Documents that ship with the Professional Edition of Microsoft Visual FoxPro version 3.0 for Windows and the Visual FoxPro Help file incorrectly list the ConnectName property as being available with the SQLGETPROP() function. However, using the... |
| 30739 | When attempting to establish a connection to a remote data source using a connection created with the Connection Designer, Visual FoxPro fails, and displays this error message: Connectivity error: [Microsoft][ODBC DLL]Data Source Name Too Long |
| 30740 | The Microsoft OLE DB SDK contains the Microsoft OLE DB Simple Provider (Msdaosp.dll) file. When you try to set a column of a simple provider by binding with type DBTYPE_STR and calling IRowsetChange::SetData() or IRowsetChange::InsertRow(), the column... |
| 30741 | If a Microsoft Excel spreadsheet's cells contain formulas, the Import function in Visual FoxPro will not import the data correctly. All or part of the data may be invalid when it is imported to the .dbf file. |
| 30742 | This article demonstrates how to use OLE automation to create a mail merge in Word for Windows 97 SR-1 using data from a Visual FoxPro (VFP) for Windows table. |
| 30743 | If you use the MFC (Microsoft Foundation Classes) ODBC wrapper classes (for example, CDatabase and CRecordset ) on one thread, and you use straight ODBC API calls on another thread in the same process, a deadlock may occur. |
| 30744 | This article describes how to use SQL pass-through technology to execute a stored procedure on an Oracle server. Oracle does not use the standard SQL EXECUTE command to execute stored procedures. |
| 30745 | When creating a connection to access remote data, you can create a connection that does not require an ODBC datasource. Because this method does not require an existing ODBC datasource, you do not have to be concerned with setting up the datasource in... |
| 30746 | When using Microsoft SQL 6.5 and MSDASQL provider with multiple ADO client-side recordsets sharing the same connection, and using a Substring on a column, the following error may appear: [Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream.... |
| 30747 | In a scenario where a cursor is open from a Remote View or SQL Pass Through connection made through the Text File ODBC driver, if you try to modify or delete a record in that cursor, one of the following errors occurs: Connectivity error:... |
| 30748 | When you open a shaped recordset, you may receive one of the following error messages: With the Microsoft SQL Server OLE DB Provider (SQLOLEDB) that ships with MDAC versions earlier than 2.5: Non-Root Provider Commands must be rowset producing. With... |
| 30749 | The OLE DB Provider for SQL Server generates sp_executesql statements when it runs the UpdateBatch method of an ADO Recordset object to run batch updates. However, the generated sp_executesql statements may not be able to reuse SQL Server query plans... |
| 30750 | This article describes how to programmatically remove an existing ODBC datasource instead of manually removing it through the ODBC Administrator. You can use the SqlConfigDataSource function in Odbccp32.dll for this purpose. |
| 30751 | Applications that use SQLXML to retrieve data from a Microsoft SQL Server stored procedure may encounter incorrect native SQL Server error information. Native SQL Server error related fields such as HRESULT, SQLSTATE, Native Error, Error state, and... |
| 30752 | Do not install Microsoft Data Access Components (MDAC) 2.6 or later on any SQL Server 7.0 clustered nodes. If you install MDAC 2.6 or later on any node in the cluster, directly or through the installation of another program, it may cause a... |
| 30753 | Service packs are the means by which Microsoft distributes bug fixes. Service packs keep a product current. Service packs include updates and may include system administration tools, drivers, and additional components, which are conveniently bundled... |
| 30754 | If an ActiveX Data Object (ADO) recordset is bound to any bound control and is then persisted to XML, the first row is not saved. |
| 30755 | When you open two recordsets with the Msdatashape provider, the second recordset has the incorrect number of records. |
| 30756 | An access violation occurs in the ODBC32!RegMonitorThread function during process shutdown. |
| 30757 | When you use the adUseServer cursor location with the default Firehose cursor (Forward-Only, Read-Only cursor), the following error is generated when you use the Recordset.Find command: Run-time error '-2147217879 (80040e29)': Rowset does not support... |
| 30758 | Microsoft Data Links provide a simple interface to test an ActiveX Data Object (ADO) connection to a data source by using an OLEDB provider or an Open Database Connectivity (ODBC) driver. The connection information specified when setting up and... |
| 30759 | When you assign an integer value to an Array typed field, the Microsoft Internet Publishing Provider (MSDAIPP) does not deny the assignment and the following error message occurs when you try to retrieve the field's value: Run-time error # 13: Type... |
| 30760 | When an ODBC API function such as SQLExecute calls a stored procedure that has a call to sp_getbindtoken or that fires a trigger that has a call to sp_getbindtoken , you may see the following error message: DIAG [22018] [Microsoft][ODBC SQL Server... |
| 30761 | If an ActiveX Data Objects (ADO) application connects to an Oracle database using Microsoft ODBC for Oracle, creates a Command object of type adCmdStoredProc with its CommandText property set to the name of the Oracle package and stored procedure in... |
| 30762 | The OLE DB Simple provider for XML (XML OSP) can be used to load the hierarchical data that is in an XML document into a read-only ADO recordset. The data can then be read and accessed by using the standard methods of the ADO Recordset object. The XML... |
| 30763 | This article describes how to get the Btrieve ODBC Interface for Windows 3.1, and the Btrieve ODBC Interface for Windows 95. |
| 30764 | If you create an ActiveX Data Objects (ADO) or ADOR recordset with a field of type adVariant, and populate that field with a Microsoft Visual Basic string value, then call the Recordset's Save method, specifying ADTG as the persistence format, the... |
| 30765 | In cases where the recordset has been sorted and the current record's data is changed, the position can also change. In such cases, the MoveNext method works normally, but be aware that the position is moved one record forward from the new position,... |
| 30766 | Using ODBC API functions such as SQLBindParameter and SQLExecDirect you can execute an INSERT statement and you can insert data into any backend database. Using ODBC API functions you can also insert null data into a particular column of a table, if... |
| 30767 | SQL Server can be installed utilizing either Standard, Windows NT Integrated or Mixed security. The Trusted Connection is available only under Windows NT. When creating a new DataSource to SQL Server via the ODBC dialog box in the Control Panel of a... |
| 30768 | When you use the ODBC Driver for SQL Server with MDAC 2.6 or later under Windows NT 4.0, you may notice a memory leak. |
| 30769 | It is possible programmatically to create an ODBC datasource rather than requiring it to be created manually through the ODBC Administrator (or through the modification of the Odbc.ini file). The SqlConfigDataSource function, found in the... |
| 30770 | The Visual FoxPro ODBC Driver Help File has conflicting information on the availability of the INDEX ON command. |
| 30771 | XPath.exe demonstrates how to extract an XML stream from a SQL Server 2000 database by using an XPath query and ADO in Visual C++. |
| 30772 | The IDataInitialize interface can be used to connect to an OLE DB datasource by using a connection string. The IDataInitialize interface is supplied by the OLE DB core components. When writing an OLE DB provider, it is important for you to know that... |
| 30773 | The SQL Server data type timestamp is a column value that is automatically updated every time a row is inserted or updated. Values in timestamp columns are not date/time data. By default, they are defined as binary(8) (for non nullable columns) or... |
| 30774 | The MFC Encyclopedia article Recordset: Declaring a Class for a Predefined Query describes how to invoke a predefined query that takes parameters and returns a result set. The instructions in that article will not work for predefined queries that... |
| 30775 | When you update a bound text box by setting its text property in code, and then you call a CancelUpdate method, the value in the field does not revert to its original value. |
| 30776 | DBCTL demonstrates a way to use ODBC in an ActiveX Control (OLE Control). A Visual C++ and a Visual Basic client application are included as part of this sample. The Visual C++ client is called DBUSR, the Visual Basic client is called DBVBUSR. The... |
| 30777 | AdoGUIDz.exe is a self-extracting executable that contains a sample project that demonstrates using the globally unique identifier datatype (GUID) with Microsoft Access, SQL 6.5 and SQL 7.0. The sample code may be particularly helpful if you are... |
| 30778 | This article contains information about the bugs that are fixed with the Microsoft Data Access Components 2.7 Service Pack 1 Refresh (MDAC 2.7 SP1a). You can obtain MDAC 2.7 SP1a by installing SQL Server 2000 Service Pack 3a (SP3a). If you have... |
| 30779 | This article discusses how the Microsoft SQL Server ODBC 2.x Driver returns the output of Transact-SQL RAISERROR or PRINT statements to an ODBC application. |
| 30780 | When you install SQL Server 2000 Service Pack 3 (SP3), SQL Server deploys version 2000.80.380.0 of the Sqlunirl.dll file. Version 2000.80.380.0 is part of Microsoft Data Access Components (MDAC) 2.7 Service Pack 1 (SP1). The correct version... |
| 30781 | When you use the NoWorkerThread connection string property with Microsoft OLE DB Provider for Oracle (MSDAORA), worker threads are still spawned when you use the provider with distributed transactions. |
| 30782 | When you try to save an ADO recordset to a file that was created by another user of the system, you may receive the following error message: Run-time error '-2147286781 (80030103)': Can't save. You receive this error message if the application is in a... |
| 30783 | This article describes the SQL Server Net-Libraries support for the QLogic card. This support is included in Microsoft Data Access Components (MDAC) 2.7 SP1 Refresh (2.7 SP1a). |
| 30784 | When you use the ODBC Driver for Microsoft SQL Server, and you execute a USE statement immediately followed by a SELECT statement in a single Batch command, the result set may contain one fewer row than when the statements were executed as separate... |
| 30785 | When you try to create global objects by using Windows 2000 Terminal Services server with Windows user credentials that are different from administrator credentials or LocalSystem credentials, the operation may fail. For example, when you try to... |
| 30786 | Microsoft Data Access Components (MDAC) is a collection of components that is used to provide database connectivity on Microsoft Windows operating systems. MDAC is a ubiquitous technology, and it is likely to be present on most Windows systems. By... |
| 30788 | This article lists the significant changes in Microsoft Data Access Components (MDAC) version 2.8 from the previous versions of MDAC. This information includes references to the online documentation, relevant Microsoft Knowledge Base articles, and... |
| 30789 | This article discusses the version of Microsoft Data Access Components (MDAC) that is installed with Microsoft Windows 2000 Service Pack 4 (SP4). |
| 30790 | This article describes how to programmatically specify the client network library in the connection string when you connect to a SQL Server database. In Microsoft Data Access Components (MDAC) 2.6 and later, you can specify the client access library... |
| 30791 | When you use the Microsoft Excel Open Database Connectivity (ODBC) Driver to connect to an Excel worksheet as an ODBC data source, the driver assumes by default that the first row of worksheet data contains column headers (field names). According to... |
| 30792 | When you install Microsoft Data Access Components (MDAC) versions 2.6 or 2.7 on a computer that is running Windows NT 4.0 or Windows 2000, you may receive the following error message: 0x80070057 The parameter is incorrect. The Dasetup.log shows that... |
| 30793 | Oracle number fields with a precision greater than 9 and with a scale of 0 are defined as type Text when they are linked into a Microsoft Access 97 database programmatically through Microsoft ActiveX Data Objects Extensions for Data Definition... |
| 30794 | With the Microsoft Jet 4.0 ODBC driver, a call to the SQLBulkOperations ODBC function, when preceded by a call to SQLExtendedFetch , may result in the following error: DIAG [S1010] [Microsoft][ODBC Driver Manager] Function sequence error (0) |
| 30795 | When you try to connect to a Microsoft SQL Server named instance by using a Canonical Name (CNAME), the client receives the following error message, and the connection fails: SQL Server does not exist or access denied ConnectionOpen (Connect()) |
| 30796 | If you issue a SHAPE command whose child recordset contains a UNION clause, and the UNION creates a single resultset from multiple different tables with different schema, the UNION works because the fields are concatenated in such a way that the... |
| 30797 | When an ADO application is redistributed, it produces the following run-time error on the user's computer: Run-time Error 430 Class does not support automation or does not support expected interface. |
| 30798 | If you persist a recordset with empty values at non-nullable columns to an Extensible Markup Language (XML) file by using the Save Method of an ADO Recordset, incorrect data is saved, and no error occurs. |
| 30799 | When Analysis Services 2000 is installed on a system that has Microsoft Visual Studio .NET Beta 2 installed, the following error may be seen when attempting to drill down on a member in the cube browser: (Unable to retrieve children: Member with the... |
| 30800 | The only legitimate redistribution mechanism for Microsoft Data Access Components (MDAC) version 2.0 or later, is the entire Mdac_typ.exe file. There are many dependencies between the MDAC components since version 2.0. Mixing different versions of... |
| 30801 | When you install Windows 2000 SP1 (MDAC 2.5 SP1) or Windows 2000 SP2 (MDAC 2.5 SP2) on a system that has MDAC 2.6 installed, the resulting system configuration will have MDAC 2.6 still installed along with updated Microsoft Jet components. |
| 30802 | When you call the Update method of an ActiveX Data Objects (ADO) recordset that is opened on a SQL statement that also contains a sub-select using the Microsoft ODBC Driver for Oracle, then the following error message occurs: [Microsoft][ODBC driver... |
| 30803 | Active Template Library (ATL) OLE DB Consumer libraries provide four types of accessors template classes to retrieve or manipulate data. ATL4Acc.exe is a sample that demonstrates data retrieval from a Microsoft SQL Server version 7 stored procedure... |
| 30804 | Accessing Visual FoxPro data using the Visual FoxPro ODBC driver version 6.0 may cause a fatal exception in the ODBC client application. |
| 30805 | This article contains sample code for an ASP that adds a new record to a Microsoft Visual FoxPro (VFP) table and inserts over 254 characters into a memo field in that table. |
| 30806 | When inserting a record into a table that has a field that does not allow nulls, records inserted through the VFPODBC driver react differently than native Visual FoxPro. When you are inserting the record into a linked table through the Microsoft... |
| 30807 | You may receive the following error running a Remote View after setting a filter condition for a bit field from a SQL Server table: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server] Line 1: Incorrect syntax near '.'. -or-... |
| 30808 | When committing a new record to a remote view, you may receive this error: Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server] The column xxx in table yyy may not be null. Where xxx is the name of the remote data's field and... |
| 30809 | When using the Setup Wizard in Microsoft Visual FoxPro 3.0b, if you select the Btrieve Driver alone in the ODBC Drivers dialog box, the error Required File Missing: MSJINT32.DL_ will occur. The error message appears after the Finish button is... |
| 30810 | When the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL) calls IDBSchemaRowset::GetRowset to retrieve DBSCHEMA_PROCEDURE_PARAMETERS with the PARAMETER_NAME restriction set to an empty string, the provider may incorrectly match the empty string... |
| 30811 | If Microsoft Data Access Components (MDAC) 2.6 Service Pack 1 (SP1) is installed immediately after installing MDAC 2.6 RTM, without restarting Windows 2000 between the two MDAC installations, the MDAC 2.6 SP1 installation may fail with the following... |
| 30812 | When you use SQL commands that return messages in an asynchronous fashion, such as the Microsoft SQL Server BACKUP ... WITH STATS command, which returns a %Complete message at points in the procedure, the command executes, but the notification... |
| 30813 | If you use the ADOX Catalogs collection and the Microsoft OLE DB Provider for Jet to retrieve the columns of a Microsoft Access table, the columns are sorted alphabetically. |
| 30814 | To install software properly on a Terminal Server computer, Terminal Server must be set in Install Mode. One way to do this is to use the Add/Remove Programs application from Control Panel to install the software. When you install Microsoft Data... |
| 30815 | Under Windows 2000 with Multilanguage User Interface installed, when you use the Microsoft ODBC for Oracle Driver to create an ODBC data source in the ODBC Administration application, a message box appears that contains only question marks. |
| 30816 | After you install Microsoft Data Access Components version 2.6, queries that use the Active Directory Services Interfaces (ADSI) OLEDB provider, ADSDSOObject, may return the following error: Error -2147221164 (80040154) : Class not registered |
| 30817 | It is possible to create a batch of SQL statements that run on Microsoft SQL Server by separating each SQL statement with a semicolon (;). You can achieve similar results when you run Oracle with either the OLE-DB Oracle Provider or Oracle driver... |
| 30818 | When attempting to create a DSN using the installable ISAM ODBC Driver for FoxPro, the following message appears: The Microsoft FoxPro driver is no longer supported, and has been replaced by the Microsoft Visual FoxPro driver. When attempting to use... |
| 30819 | When creating a remote view to a FoxPro table using the Visual FoxPro ODBC driver, the following error occurs when you set a Left Outer Join in the Join tab between two tables: Connectivity error: [Microsoft][ODBC Visual FoxPro Driver]Command Contains... |
| 30820 | This article lists the locations of the available release manifests for Microsoft Data Access Components (MDAC) products. |
| 30821 | When using the 16-bit Oracle 7 ODBC driver (Sqora7.dll version 1.11.0000) that ships with Visual FoxPro to connect to an Oracle 7 server, the connection fails with the following error message: Connectivity Error [Microsoft][ODBC DLL] Driver's... |
| 30822 | If you load Microsoft Office 97 prior to loading Visual FoxPro version 3.0 or 5.0 you receive the following error messages during the Visual FoxPro installation: Unable to load installable ISAM Can't load mspdox35.dll (error code=[error code]).... |
| 30823 | Microsoft OLE DB Provider for SQL Server does not support nested transactions, and the following error message is returned: Could not start a transaction for OLE DB provider '%ls'. Microsoft SQL Server also returns the following error message if the... |
| 30824 | When you use Distributed Component Object Model (DCOM) to connect to an ActiveX EXE file that connects to a Microsoft Jet database on a different server, you receive the following error message: 80004005 The Microsoft Jet database engine cannot open... |
| 30825 | If an application connects to a database using the Microsoft Access ODBC Driver or the Microsoft OLE DB Provider for Jet version 4.0, and if the application uses the Now function of the Visual Basic for Applications in the WHERE clause of a SQL query,... |
| 30826 | An empty recordset is returned when you use Remote Data Objects (RDO) to pass a character type parameter from Microsoft Visual Basic to Microsoft Access. |
| 30827 | This article explains how to persist and use Microsoft Data Links programmatically with Microsoft Visual Basic and Microsoft Visual C++. |
| 30828 | When you open an ActiveX Data Objects (ADO) recordset with pessimistic locking on already locked data and then check the recordset for the EOF property, you receive different results on Microsoft SQL Server 6.5, Microsoft SQL Server 7.0, and Microsoft... |
| 30829 | While you run setup on a computer that has Microsoft Windows version 3.x (16-bit Windows) installed from image disks created using the Microsoft Visual FoxPro Setup Wizard, the following error appears: Setup Parse Error in Initialize pass Object ID... |
| 30830 | There are several ways to change a Microsoft Access table name in a Visual Basic application, some of which include the use of SQL, OLE automation, or Microsoft ActiveX Data Objects Extensions for Data Definition Language and Security (ADOX). The... |
| 30831 | A recordset may lose synchronization in Microsoft Internet Explorer if both of the following conditions are true: You pass back an empty Microsoft ActiveX Data Objects (ADO) Recordset object to Microsoft Internet Explorer by using the Remote Data... |
| 30832 | Microsoft Data Access Components (MDAC) 2.5 is the earliest version of MDAC that can be installed on a Microsoft Windows 2000-based computer. |
| 30833 | Session Summary Thursday, June 19, 2003 This Microsoft Support WebCast provides an overview of the main security features that are introduced in Microsoft Data Access Components (MDAC) 2.8. This is a Level 300 session that will be presented by Ammar... |
| 30834 | When a SELECT DISTINCT statement is used with the Microsoft ODBC for Oracle driver, the following error may occur: DIAG [HYC00] [Microsoft][ODBC driver for Oracle]Cannot use Keyset-driven cursor on join, with distinct clause, union, intersect or minus... |
| 30835 | The Adomd.exe self-extracting executable illustrates how to retrieve actions, functions and sets OLAP schema rowsets from the Microsoft OLE DB Provider for OLAP Services (MSOLAP) that is included with Microsoft Data Access Components (MDAC) 2.6. These... |
| 30836 | This article describes how to create a Remote View programmatically in Visual FoxPro to access data that resides in a Microsoft Excel spreadsheet (.xls file). |
| 30837 | When using an input parameter in a WHERE clause whose size is greater than the column size in the database, the Microsoft ODBC for Oracle driver returns SQL_SUCCESS_WITH_INFO on the SQLExecute call with a SQLState 01004. |
| 30838 | The ODBC Microsoft Desktop Database Drivers Help documentation contains an error for the ODBC Microsoft Access Setup. The Page timeout in the Options section is incorrect. |
| 30839 | Microsoft does not provide any supported tool to allow tracing of OLE DB API calls. The Trace Provider tool that ships with the Microsoft Data Access Components (MDAC) version 2.5 Software Development Kit (SDK) is a beta tool and, due to design... |
| 30840 | The Microsoft OLE DB Provider for SQL Server (SQLOLEDB) is slower in inserting or updating BLOB data types such as text , ntext , or image when compared with the Microsoft OLE DB Provider for ODBC drivers (MSDASQL). |
| 30841 | Prior to the MDAC 2.5 release, users were able to use a number of methods to install the Microsoft Data Access Components (MDAC). In addition, it was possible to install the MDAC components with Microsoft Visual Studio 6.0 (or any of its released... |
| 30842 | When you call an Oracle procedure that returns an ADO recordset through the Microsoft ODBC driver for Oracle, one of the following error messages may occur: Microsoft OLE DB Provider for ODBC Drivers (0x80040E14) [Microsoft][ODBC driver for... |
| 30843 | In the ODBC Data Source Administrator, you see two versions of a Microsoft ODBC driver: a standard version and a localized version. An example of two versions of the Microsoft ODBC driver for Oracle, using the French localized version, is shown here:... |
| 30844 | Queries that show as fully optimized in Microsoft Visual FoxPro might run very slowly through the Microsoft Visual FoxPro ODBC driver. |
| 30845 | If connection pooling is enabled for the following ODBC drivers: Microsoft Visual FoxPro Driver Microsoft FoxPro VFP Driver (*.dbf) Microsoft dBase VFP Driver (*.dbf) The following error may occur: Exception occurred within ODBC driver driver name... |
| 30846 | When you use data access technologies such as Microsoft Data Access Objects (DAO) or Microsoft ActiveX Data Objects (ADO) to open text files that contain a non-standard delimiter (such as a single quotation mark), the delimiter appears in the field... |
| 30847 | Queries that contain more than 510 parameters may cause the following error messages to occur when you use the Microsoft ODBC driver for Oracle: Relational data provider reported error: [Microsoft][ODBC driver for Oracle]Syntax error or access... |
| 30848 | When you use Visual Basic Scripting Edition (VBScript) to perform a numeric comparison or calculation on an adNumeric (131) field type, you may receive the following error messages: Microsoft VBScript runtime error '800a000d' Type mismatch -and-... |
| 30849 | When the default language is set to JScript for Active Server Pages (ASP) connecting to a file-based database (for example, Access, Visual FoxPro) returns an error such as the following: Microsoft OLE DB Provider for ODBC Drivers error '80004005'... |
| 30850 | One of the following errors occurs when passing a date to a SQL Stored Procedure: Microsoft OLE DB Provider for ODBC Drivers error 80004005 At least one parameter contained a type that was not supported. -OR- Microsoft OLE DB Provider for ODBC Drivers... |
| 30851 | When you use ActiveX Data Objects (ADO) and ODBC to try to connect to a Microsoft Access database, you may receive the following error message: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access 97 Driver]... |
| 30852 | When you use ActiveX Data Objects (ADO) or ODBC to connect to a Microsoft Access database, you may receive the following error message: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access 97 Driver] The... |
| 30853 | When you open a Schema Recordset, such as adSchemaColumns or adSchemaProviderTypes, against Microsoft SQL Server 2000, the BIGINT data type is mapped to adChar (129) instead of adBigInt (20). |
| 30854 | When you use an ADOX key object collection to retrieve the primary key column information of a Microsoft Access table or SQL Server table, a C++ exception may occur. Microsoft Visual Basic code may return the following error: operation is not... |
| 30855 | The Ospxml.exe sample demonstrates how to retrieve hierarchical ActiveX Data Objects (ADO) recordsets from an arbitrary XML document using the Microsoft OLE DB Simple Provider (MSDAOSP) that ships with Microsoft Data Access Components (MDAC) version... |
| 30856 | If you try to use Properties in a SQL statement with an out-of-process ADODB component, the Microsoft OLAP provider results in one of the following error messages: (-2147467259) The data provider or other service returned an E_FAIL status. -or-... |
| 30857 | According to Microsoft Knowledge Base article 275561 ACC2000: New Features in Microsoft Jet 4.0: To minimize the impact of the increased page size and respond to a long-standing request from developers building applications based on the Microsoft... |
| 30858 | This article describes how to contact Microsoft for help with the following issues: Replace lost, broken, damaged or defective Microsoft software disks. Purchase product upgrades. Replace broken or defective Microsoft hardware products. Check the... |
| 30859 | When you use the Microsoft Remote provider to run a parameterized query against a remote database, the Requery method of the ADODB.Recordset object fails with the following error message: Unknown Error (80040e4b). |
| 30860 | When you save a UDL file, the Connect Timeout (DBPROP_INIT_TIMEOUT) value is not persisted. When you save a UDL file, the Connect Timeout (DBPROP_INIT_TIMEOUT) value is not persisted. STATUS This behavior is by design. |
| 30867 | This article presents a list of all the files installed by MDAC 2.1.1.3711.11 (General Availability) MDAC 2.1 (GA) (Mdac_typ.exe) can be downloaded from the following Web site: Microsoft Data Access Components (MDAC) and Data Access SDK Download Page... |
| 30868 | This article presents a list of all the files installed by MDAC 2.1.2.4202.3 (GA). You can download MDAC 2.1 Service Pack 2 (Mdac_typ.exe) from the Microsoft Universal Data Access download Web page:... |
| 30869 | When you use Microsoft ODBC Driver for SQL Server to fetch data in asynchronous mode, you may see that the data that is fetched is corrupted for some of the columns. This corruption does not always occur, and is random in nature. Most of the time you... |
| 30870 | If you turn off OLE DB session pooling and run the Visual Basic Bank sample program three times in succession, you receive the following error message on the third iteration: -2147217900 [Microsoft][ODBC SQL Server Driver][SQL Server]Distributed... |
| 30871 | Microsoft Data Access Components (MDAC) 2.1 provides a CAB file version of the installation package. However, the CAB file version of the installation package is not available in MDAC 2.1 Service Pack 2 (SP2). This problem pertains only to MDAC 2.1... |
| 30872 | In certain cases, you may want to determine if a Primary Key is defined on an underlying database table and if so, what columns are used in that Primary Key. You can obtain this information by using Microsoft ActiveX Data Objects Extensions for Data... |
| 30873 | Beginning with Windows 2000, the Microsoft Data Access Components (MDAC) are considered an integral part of the operating system. As a result, the MDAC 2.5 service packs are included as part of the Windows 2000 service packs. Windows 2000 Service Pack... |
| 30874 | This article deals with redistribution of Microsoft Data Access Components (MDAC), which includes ODBC, OLE DB, ADO, RDS, the MDAC Standalone, MDAC Redistribution and the Data Access SDK. |
| 30875 | Installing Microsoft Data Access Components MDAC 2.6 RTM on Windows 2000 or Windows NT 4.0 Professional, Server, or Advanced Server-based computers prevents error text description from being returned from the Microsoft OLE DB Provider for SQL Server... |
| 30876 | When you install Microsoft Data Access Components (MDAC) version 2.6 or later on a computer that is running Microsoft Windows 2000 or Microsoft Windows XP, either the installation program completes but does not actually install MDAC, or it displays a... |
| 30877 | If you try to save a Project 98 project to an Oracle database using an ODBC data source name (DSN) and the Microsoft ODBC for Oracle driver on a computer that is running the German or the Japanese version of Microsoft Windows 2000, you receive the... |
| 30878 | Microsoft Data Links, provided with the Microsoft Data Access Components 2.0, provide a convenient and standard way to create and validate the connection string syntax used with an ODBC Driver or OLE DB Provider. Even if you do not reference the data... |
| 30879 | For your Microsoft ActiveX Data Objects (ADO), ODBC, OLE DB or Remote Data Services (RDS) applications to work properly you must distribute Microsoft Data Access Components (MDAC) with your application. This article discusses Microsoft Data Access... |
| 30880 | When you add a new record to a grouped data access page, the page unexpectedly closes. You receive no error message or warning message. The page simply disappears, and then either Microsoft Access or Microsoft Internet Explorer also quits, depending... |
| 30881 | Microsoft Works 4.5a incorrectly installs the following OLE DB component Dynamic-Link Libraries (DLLs) into the Windows system folder (for example, C:\Winnt\System32) instead of the proper location. The following files should be placed in... |
| 30884 | Often, operations involving a database can take some time to process a query, connect to a datasource, or retrieve results to a client. ADO provides a way to perform these operations asynchronously. With this ability, developers can also do other... |
| 30885 | In an application, sometimes it is useful to determine the properties of fields in a remote datasource. You can determine information such as the field names, data types and field lengths by examining the Fields collection of the ActiveX Data Objects... |
| 30886 | ActiveX Data Objects (ADO) Hierarchical recordsets greatly resemble parent- child relationships created using the SET RELATION command in native FoxPro language. Hierarchical recordsets are created using a series of SQL statements in conjunction with... |
| 30887 | Dbf2rs.exe is a self-extracting executable that contains a Visual FoxPro program named Dbf2rs.prg, which shows how to convert a Visual FoxPro cursor to an ActiveX Data Objects (ADO) recordset. The executable file also contains the necessary ADO... |
| 30888 | This article describes how to use offline ActiveX Data Objects (ADO) 2.x recordsets in Visual FoxPro 6.0. |
| 30889 | When you try to specify a connection string to use the persist provider to open from a valid ADO stream object, you receive the following error message: Run-time error '3001': Arguments are of the wrong type, are out of acceptable range, or are in... |
| 30890 | If you pass an ADO recordset by using a ByRef method parameter to an out-of-process COM object and the out-of-process COM object generates an error, this error information may not be properly reported to the client application. If you pass an ADO recordset by |
| 30891 | On a Windows 2000-based computer, when you close down an application or service that uses the Mtxdm.dll file (version 1999.9.3421.3), the application or service may experience an Access Violation. This problem is most likely to occur in applications that are using ODBC connection pooling. |
| 30892 | This article assumes intermediate knowledge of ATL, ADO and RDS technologies. This article demonstrates one way to pass an array of Recordsets from an ActiveX Data Objects (ADO)/Remote Data Service (RDS) server. |
| 30894 | If you try to access the methods or properties of an RDS DataControl object that has been executed asynchronously, you see one of the following errors: Run-time error '4113': Can't perform operation with an async operation pending -or- Run-time error '4113': Operation cannot be performed while |
| 30895 | Within your MDAC code, you have multiple recordsets with the same recordset object that are created off of the same command and are also pointing to the same connection. The first recordset that is opened contains multiple recordsets within that same... |
| 30896 | When you debug an application that uses ODBC in the Visual C++ debugger, the debugger appears to hang for a period of time when loading ODBCINT.dll. |
| 30897 | On a computer with the original release of Windows 95 (version 4.00.950), if you run the Microsoft Data Access Components (MDAC) standalone setup program, the dialog box for the setup program appears 10-20 times wider than the screen. If you slide the... |
| 30898 | When a query is run on one thread and canceled on another, the thread that executes the query with SQLExecute() is not notified by the return values that query was canceled. |
| 30899 | Session Summary February 10, 2003 In this session, we will discuss three areas related to Microsoft Data Access Components. The categories covered will be General Background Information, Tools and Special Considerations, and Installation... |
| 30900 | SQLBrowseConnect may cause an Access Violation in the client Application |
| 30901 | An internal consistency (IC) error occurs when you attempt to view the properties of a connection using SQLGetProp in the DEBUG window. An internal consistency (IC) error occurs when you attempt to view the properties of a connection using SQLGetProp in the |
| 30902 | When you use the System.Data.SqlClient.SqlConnection class to connect to a Microsoft SQL Server database with protocol encryption enabled, one or more objects in the .NET-managed heap can be corrupted. This causes the Microsoft .NET application to... |
| 30903 | When leaving the ODBC Drivers check box blank in step 2 of the Setup Wizard in Visual FoxPro 3.0, the desired effect is to avoid having the ODBC files copied to the disk images. The problem is that some of the ODBC files get copied to the disk images even if the ODBC check box is clear. There are at |
| 30904 | The following error occurs after disconnecting from Sybase server and reconnecting: VFP caused an invalid page fault in module LIBCOMN.DLL This error occurs if the SQLCONNECT() function is used for connecting, and two or more connections have been made to Sybase 10 or 11. When any connection |
| 30905 | Client computers that have Microsoft Data Access Components (MDAC) version 2.6, or later, can try multiple protocols or Interprocess Communication (IPC) mechanisms to establish connections to SQL Server. |
| 30906 | When you upgrade from Microsoft Data Access Components (MDAC) 2.6 (that is included with SQLXML 2.6) to MDAC 2.7 (that is included with SQLXML 3.0), you find that GUID data that is retrieved through SQLXML does not contain opening and closing braces (... |
| 30907 | After you apply a sort clause that contains a column of 255 bytes to a disconnected ADO Recordset, in certain cases, repeated AddNew calls cause an Unspecified error to be reported. RESOLUTION A supported fix is now available from Microsoft, but it is only |
| 30908 | In an application that uses the Microsoft SQL Server-specific bulk-copy (BCP) ODBC application programming interface (API) extensions, and that has ODBC connection pooling turned on, an access violation occurs when you execute functions such as... |
| 30909 | When you set a recordset to use client-side cursor and the BatchOptimistic lock type, there is no update to the database until you call the UpdateBatch method. However, if the DataGrid is bound to the DataEnvironment object, it does not work as expected. Any update to the DataGrid sends to the database |
| 30910 | When ActiveX Data Objects (ADO) queries a table that contains a numeric or decimal value with a precision that is greater than 28, you receive the following error message: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. |
| 30911 | When using the OLE DB Templates with a SQL Server database, it is often necessary to add records to a table that contains an identity column. Getting an identity column to increment properly with the OLE DB for ODBC provider that ships with Visual C++ 6.0, Msdasql.dll, requires that the |
| 30912 | When an application that uses multiple threads that share a global environment handle implements Open Database Connectivity (ODBC) connection pooling, the application may stop responding (hang) on the platforms listed above with MDAC version 2.5 or... |
| 30913 | With the SQLOLEDB provider that ships with MDAC version 2.5 or 2.5 SP1, calling a Microsoft SQL Server stored procedure with one or more PRINT statements that return more than 512 bytes of data each may result in an access violation. The error message... |
| 30914 | Beginning with Windows 2000, the Microsoft Data Access Components (MDAC) are considered an integral part of the operating system. As a result, the MDAC 2.5 service packs are included as part of the Windows 2000 service packs. Windows 2000 Service Pack... |
| 30915 | On an ODBC connection to a SQL Server 2000 server, the second call to the SQLExecute function on a prepared statement may cause a client-side access violation (AV) if the statement attribute SQL_ATTR_NOSCAN is set to SQL_NOSCAN_ON prior to execution. RESOLUTION To |
| 30916 | After you install Microsoft Data Access Components (MDAC) version 2.6, and you try to copy and paste an OLAP object from OLAP Manager or use the Cube/Dimension Editor to add a new object, you may receive the following error message: Arguments are of... |
| 30917 | Running a certain sequence of commands involving explicit transactions and parameters in an application program using the SQLOLEDB Provider incorrectly leaves an uncommitted transaction open. This can cause severe blocking and other problems. |
| 30918 | With the Microsoft OLE DB provider for SQL Server (SQLOLEDB), if you try to access a database on a remote SQL Server that doesn't exist on a local SQL Server, the following error may occur: Cannot open database requested in login 'database name'.... |
| 30919 | Applications that call the LoadLibrary and FreeLibrary functions for a dynamic-link library (DLL) that uses Odbc32.dll may receive the following error message when multiple instances of the application are running under a heavily stressed environment: YourApp.EXE - Application Error: The instruction |
| 30920 | When you call the ODBC function SQLConnectW and supply non-null terminated strings for the data source name (DSN), user ID (UID), or password (PWD) parameters along with length indicators indicating the exact byte length of the strings, this may later... |
| 30921 | This article lists article numbers for bugs that were fixed in Microsoft Data Access Components (MDAC) Service Pack 3 (SP3). |
| 30922 | Service packs are the means by which Microsoft Data Access Components (MDAC) bug fixes are distributed. Service packs keep the product current. Service packs may include updates, system administration tools, drivers, and additional components. All are... |
| 30923 | With Microsoft Visual Basic versions 4.0, 5.0, and 6.0 for Windows, you can specify your ODBC (Open Database Connectivity) driver and server in your connect string when using RDO (Remote Data Object) and DAO (Data Access Objects) which eliminates the... |
| 30924 | When setting the password property of the RemoteData Control (RDC) at design time in the Property Window, asterisks are not substituted for the password characters. When the ODBC dialog box is displayed, the password is converted into asterisks. |
| 30925 | Using Microsoft Jet version 4.0, sorting is different than in previous versions. For example, assume you have the following records in an Access table: FIELD1 W W- WB W-B In previous versions of the Jet database engine, issuing SELECT * FROM Table1... |
| 30926 | This article provides information about the bugs that are fixed with the Microsoft Data Access Components version 2.7 Service Pack 1 (MDAC 2.7 SP1). To download MDAC 2.7 SP1, visit the following Microsoft Web site:... |
| 30927 | When you use the DTPicker to update a table, you may receive the following error message if an intrinsic control is also updating the table: Consumer's event handler called a non-reentrant method in the provider. If just the DTPicker is doing an update, no error is returned, but the table is not |
| 30928 | An application that uses the Open Database Connectivity (ODBC) application programming interface (API) to call a SQL Server 2000 stored procedure that has a return value with the SQLExecDirect() API function and open a cursor on the resulting table may return the following errors: szSqlState = |
| 30929 | Multithreaded Java applications that use ActiveX Data Objects (ADO) to open, query, and close connections on each thread will experience an access violation (AV) after a large number of threads have been created and destroyed. The AV usually occurs... |
| 30930 | If you program ActiveX Data Objects Extensibility (ADOX) to set the default value for the Column property, the value is not set properly. The default value is set to nothing instead of the value that you specified. When you run the project in Visual... |
| 30931 | When running a stored procedure with the SQL Server ODBC driver that ships with Microsoft Data Access Components (MDAC) version 2.6, you may receive the following error message: [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax... |
| 30932 | If you add any non-ODBC counter together with any ODBC counter in Performance Monitor (PerfMon), you do not see any activity for the ODBC Counters. CAUSE This is a bug in ODBC Driver Manager. When any non-ODBC counter is present in the list, the Driver Manager |
| 30933 | If you are using a multi-processor computer, and you call Recordset.Sort on an ActiveX Data Objects (ADO) recordset that you opened by using the adAsyncFetch flag, more FetchComplete events may be fired after the initial FetchComplete is fired. The expected behavior is that a FetchComplete event is |
| 30934 | When you use an OLE DB or an ADO application that uses the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL) to try to retrieve data from a updateable cursor, or when you try to update, to insert, or to delete data in a cursor, you may receive the following error message: Query cannot be updated |
| 30935 | If you run a remote stored procedure with output parameters on a linked server through an ODBC driver for SQL Server, the ODBC driver cannot retrieve the output parameter and you may receive the following error message: [Microsoft][ODBC SQL Server... |
| 30936 | After deleting a row and doing a MoveNext or MovePrevious, the current record is wrong. Exhibited behavior indicates that the current record will either become another record from within the recordset or EOF depending on the size of the recordset. |
| 30937 | When you are trying to use Microsoft Data Access Components (MDAC) in your applications, you may receive one of the following error messages: Error in the DLL. -or- Provider can not be found. Ensure that the provider has been installed properly. -or-... |
| 30938 | If a user opens an ActiveX Data Object (ADO) recordset by using the OLE DB Provider for SQL Server, sets the CursorLocation property to adUseServer, uses the WithEvents keyword, updates the same record more than once, and then executes a Move method... |
| 30939 | When attempting to Filter Data using the Filter option in an application generated by the Visual InterDev 1.0 Data Form Wizard or when returning an ADO Recordset when using AbsolutePaging, PageSize, and the Filter properties, incorrect results... |
| 30941 | When you perform a mail merge in Microsoft Word 97 for Windows using a Visual FoxPro table contained in a database container, the following error message appears: Word was unable to open the data source. |
| 30942 | An attempt to use an OPENXML statement after an XML document has been mapped in memory and presented to the SQL Server server may return an error if following conditions are true: The error that is returned resembles the following: ?MSSQLError... |
| 30943 | When you read negatively scaled numeric values from an ODBC driver by using the OLE DB Provider for ODBC (MSDASQL) with the ActiveX Data Objects (ADO) adUseClient cursor enumeration, the values that are returned are truncated. |
| 30944 | When you use the oj outer join syntax with a parameter in a SELECT statement using the Microsoft SQL Server driver with a SQL Server 6.5 back end, the following error message is returned: [Microsoft][ODBC SQL Server Driver]COUNT field incorrect or... |
| 30945 | You may see a memory leak when repeatedly loading and unloading the Microsoft OLE DB provider for SQL Server (SQLOLEDB) and connecting to a Microsoft SQL Server database. You may see the same behavior when using the Microsoft OLE DB provider for ODBC... |
| 30946 | In Microsoft Visual Basic ActiveX Data Objects (ADO), when connecting through the SQL Server ODBC Driver, using adFilterConflictingRecords does not filter all the conflicting records as expected. |
| 30947 | The Microsoft ActiveX Data Objects (ADO) technology allows users to obtain a recordset from a data source, disconnecting that recordset from its source by setting the Recordset of the ActiveConnection property object to Nothing, and then... |
| 30948 | When you use the Microsoft Oracle OLE DB Provider (MSDAORA) to open an ADO Recordset on a SELECT statement that contains a UNION in a sub-select query, you may receive the following error message: Unspecified Error |
| 30949 | Sometimes client computers that are running Microsoft Windows 98 Second Edition (SE), and that use MDAC 2.7, cannot connect to a named instance if Microsoft SQL Server 2000. Instead, they may receive the following connection error message: [TCP/IP... |
| 30950 | The Visual Studio 6.0 Service Pack 3 Readme refers to updates that were not included in the service pack. The Readme.htm file incorrectly states that customers can go to the Visual Studio Home Page to obtain these updates. |
| 30951 | After you install Microsoft Data Access Components (MDAC) version 2.6 or 2.7 on a Multilanguage User Interface (MUI) Microsoft Windows 2000 computer, you do not see localized error messages related to data access. All the localized error messages... |
| 30952 | This article requires a good knowledge of Component Object Model (COM), Microsoft Transaction Server (MTS), and any language to build COM components like Microsoft Visual Basic or Visual C. Multiple connections accrue on a SQL Server database or other... |
| 30953 | Using ActiveX Data Objects (ADO), when you implicitly prepare a recordset by calling RS.Fields.Refresh method, the metadata information (for example, BASETABLENAME, BASECOLUMNNAME, KEYCOLUMN) is not available. There are no errors generated when... |
| 30954 | If a deadlock condition occurs on Microsoft SQL Server in an application that uses the open database connectivity (ODBC) cursor library, a function call to the ODBC API SQLExtendedFetch returns SQL_SUCCESS instead of SQL_ERROR . This return is... |
| 30955 | When ODBC connection pooling is enabled, if database servers are down or unavailable due to network connectivity issues, Internet Information Server (IIS) or Microsoft Transaction Server (MTS) may stop responding (hang). |
| 30956 | Identity columns are normally read-only because the server generates the values. However, when you migrate data from one table to another you often want to keep the existing Identity column values rather than use server-generated values. Microsoft SQL... |
| 30957 | The Server drop-down list may be empty even if you have Microsoft SQL Server (for example, version 7.0 or version 6.5) installed on your network. The Server drop-down list is empty if the following conditions are met: You have clicked Microsoft OLEDB... |
| 30958 | When you use an OLE DB application, or an ActiveX Data Objects (ADO) application, and you execute a stored procedure against SQL Server 2000, Error 8144 occurs and Microsoft SQL OLE DB Provider (SQLOLEDB) rolls back the transaction automatically... |
| 30959 | When you attach an ActiveX Data Objects (ADO) Recordset to the Microsoft ADO Data Control, the following error message occurs: Run-time error '-2147417848 (80010108)': Method 'Recordset' of object 'IAdodc' failed |
| 30960 | In a SQLConfigDataSource ODBC function call, the Microsoft Access/Jet 4.0 ODBC driver allows you to specify a sort order as part of the CREATE_DB attribute, where sort order might be General, Arabic, Czech, Japanese, Russian, and so on. The... |
| 30961 | When using the Java Database Connectivity (JDBC) - Open Database Connectivity (ODBC) bridge to insert or update dates prior to 01-01-1900 into SQL server (version 6.5 and 7.0), the following error occurs consistently: 22008 [Microsoft][ODBC SQL... |
| 30962 | When you insert a date prior to the year 1753 by using Microsoft Access ODBC Driver, the following error message is displayed: [22008] [Microsoft][ODBC Microsoft Access Driver]Datetime field overflow (null) |
| 30963 | When you use Microsoft's Oracle ODBC driver with the ODBC SQLDescribeCol function, incorrect values may be returned for the column name and column name length. |
| 30964 | When you update a Microsoft Access table from Visual FoxPro using the Microsoft Access ODBC Driver and the string value being updated is shorter than the actual field width, extra spaces are added to the end of the string. |
| 30965 | In the Remote View Wizard, after selecting Microsoft Excel as your data source and subsequently choosing a Microsoft Excel spreadsheet, you receive this error message: Error connecting Excel Files |
| 30966 | If you apply Microsoft Data Access Components (MDAC) version 2.6 to a computer that is running Windows NT 4.0 Microsoft Message Queue Server (MSMQ), you may receive c00e0013 errors with the following text: 'No connection with sites controller' |
| 30967 | If you try to open a Microsoft Excel 4.0 file, the ODBC Microsoft Jet driver may return the following error message: [Microsoft][ODBC Excel Driver] The Microsoft Jet database engine could not find the object 'ODBCTest.xls'. Make sure the object exists... |
| 30968 | When you try to create a data source name (DSN) with the Microsoft Text Driver on a computer that has MDAC 2.1 or later installed, you may get the following error: Failed to save table attributes of (null) into (null). |
| 30969 | When you create a Visual C++ Microsoft Foundation Classes (MFC) AppWizard EXE or DLL with database support, if you select an Oracle data source name (DSN) that is associated with the Microsoft ODBC Driver for Oracle, AppWizard doesn't list the local... |
| 30970 | The Microsoft 32-bit ODBC drivers fail when called from a 16-bit application through the ODBC thunking layer. Particularly under Windows 95 and Windows 98, you will not be able to connect without the application failing. |
| 30971 | Under stress, when multiple threads are using ADO, an access violation occurs. This is most likely experienced on a busy Web server, but is not limited to that environment. This can occur even if you are not sharing ADO objects across threads. NOTE:... |
| 30972 | When you attempt to store the Microsoft Visual Basic keyword EMPTY to an ADODB Record column based on a Date field, the following error message occurs: With MDAC 2.5: Run-time error '-2147217887(8004e21)': Multiple-step operation generated errors.... |
| 30973 | The WriteText method of an ADO Stream object whose charset property is set to ascii fails after you install Microsoft Data Access Components (MDAC) 2.6 on a computer that is running Microsoft Windows 98, Windows NT 4.0 Workstation, or Windows NT 4.0... |
| 30974 | If you use the Microsoft Access (Jet) ODBC driver (Odbcjt32.dll version 4.0.5303.1), which is shipped with Microsoft Windows 2000 Service Pack (SP) 1, when you run statements that contain computed columns of a text data type, a call to the... |
| 30975 | With the advent of Microsoft Data Access (MDAC) 2.0, Remote Data Service (RDS) implements a new security feature called Handlers. These handlers are located in your Operating System root directory (that is, C:\Winnt\) inside the file Msdfmap.ini. The... |
| 30976 | SYMPTOMS When using the SQLOLEDB provider with client side cursors and prepared statements, the performance is slower than with SQL Server 6.5 and ODBC. When tracing the SQL statements sent by the client application with SQL Server Profiler, a sequence |
| 30977 | SUMMARY SQL Server allows you to choose from a number of different network libraries that you can use when connecting. You can configure these network libraries when you create a data source name (DSN) for your data source. However, an alternative way |
| 30978 | You may encounter a variety of ODBC error messages when accessing dBase databases which had been successfully accessible with prior versions of the Microsoft dBase Driver. |
| 30979 | SUMMARY A SQL Server timestamp column automatically updates every time a row is inserted or updated. Despite the name, a SQL Server timestamp column is not based on the system time and does not contain a date or time value. Instead, the timestamp |
| 30980 | Service Pack 5a for SQL Server 6.5 provides an optional installer for Microsoft Data Access Components 2.1 (MDAC 2.1). |
| 30981 | In an ADO application, when you try to retrieve datetime values from Microsoft SQL Server 2000 by using the Microsoft OLE DB Provider for SQL Server (SQLOLEDB), the seconds portion of the datetime values are rounded up randomly if the time portion has... |
| 30982 | SYMPTOMS When you call the Open method of an ADO client-cursor Recordset object that has been opened and closed previously, an access violation may occur if you change the LockType parameter of the method from adLockOptimistic to adLockReadOnly. |
| 30983 | When Microsoft Internet Explorer displays a Web page that uses Remote Data Services (RDS), an access violation may occur in Internet Explorer, and you may receive the following error message: Microsoft Internet Explorer has encountered a problem and... |
| 30984 | SYMPTOMS When opening and closing multiple ODBC SQL pass through type recordsets using DAO 3.6, the number of ODBC connections to the backend database increases with each opened recordset. |
| 30985 | When you use Microsoft ActiveX Data Objects (ADO) to retrieve data, an access violation occurs in Oledb32.dll. |
| 30986 | SUMMARY When a Unicode application calls the SQLBindParameter function with the SQL_WCHAR SQL type, the ODBC Driver Manager does not convert the SQL type to SQL_CHAR before it passes to an ANSI driver. However, the ODBC Driver Manager does convert the |
| 30987 | Because Microsoft Excel is such a powerful data analysis tool, Visual Basic and VBA application developers often want to bring data into an Excel worksheet for analysis purposes. This article describes the ActiveX Data Objects (ADO) approach to this... |
| 30988 | SUMMARY This article explains how to create a report without binding the report to any data at design time. This allows you to generate a report without knowing the column names within the Data Source. |
| 30989 | If you use Microsoft ODBC Driver for SQL Server 2000, and the ODBC API SQLDesribeParam function is used to describe the parameter marker of a query that involves an outer join, you receive the following error messages: [Microsoft][ODBC SQL Server... |
| 30990 | SYMPTOMS If you run the OpenSchema(adSchemaTables) method of an ActiveX Data Objects (ADO) Connection object against an Excel 2000 database/workbook (.xls file) with the Microsoft OLE DB Provider for Jet 4.0, the TABLE_TYPE for Worksheets in the |
| 30991 | Web servers and COM+ applications may experience blocking and 100 percent CPU usage when they use OLE DB session pooling. Two significant changes were made to the Microsoft OLE DB session pooling code to help alleviate blocking and the 100 percent CPU... |
| 30992 | SYMPTOMS An MFC database application cannot update a dynaset-type CRecordset based on a View in a SQL Server 6.00 data source, even if the operation observes the SQL Server requirement that updates through Views only update a single base table. The |
| 30994 | When you use a client-side cursor against an Oracle database with the Microsoft ODBC Driver for Oracle, a deferred update is not successful and you receive the following error message: 0x80004005 (Insufficient base table information for updating or... |
| 30995 | This article outlines some of the common steps to take when you troubleshoot a problem with a connection to an Oracle Database from an Active Server Pages (ASP) application. Some of the more common error messages are: Microsoft OLE DB Provider for... |
| 30996 | Session Summary During this session, we will discuss the differences between ODBC Connection Pooling and OLEDB Session Pooling. We will also talk about different ways to implement pooling from different programming models. This is a Level 200 session... |
| 30997 | The ADO Client Cursor Engine may leak memory when you use it with a custom, third-party OLE DB provider. The leak occurs if the custom provider does not support some common OLE DB properties in the DPROPSET_DATASOURCEINFO and DBPROPSET_ROWS |
| 30998 | When you attempt to run simple ActiveX Data Objects (ADO) code in an application, the following error can occur: Method '~' of Object '~' Failed |
| 31001 | After the release of this bulletin, it was determined that the vulnerability that is addressed is not with the OpenRowSet command. The OpenRowSet command is a Microsoft SQL Server command. Instead, the vulnerability is with the underlying MDAC... |
| 31003 | Microsoft COM+ continuously tries to unload OLE DB and succeeds. When OLE DB is unloaded, the session pool and its threads are freed. At the same time, new calls are being made into OLE DB, which causes the DLL to load again and the session pool to be... |
| 31004 | You may disable various Schannel encryption algorithms such as RC4 to enforce FIPS 140-1 compliant encryption on a computer that is running Microsoft Windows. If you have a server that is running SQL Server on this computer, and if you enab |
| 31005 | When you attempt to add a system or user data source name (DSN) to a Microsoft Access database, the ODBC Microsoft Access Setup window may not appear after you select Microsoft Access driver from the drivers listed in the Create New Data Source window. |
| 31006 | This session provides an overview of the MDAC product, its release history, and information about recent releases. An overview of the new features of MDAC 2.5 and XML Support will also be discussed. |
| 31007 | Session Summary This session provides an overview of the new features in Microsoft Data Access Components (MDAC) 2.6. Additionally, we will discuss, among other things, how the various MDAC components have been enhanced to incorporate XML. We will... |
| 31008 | This Support WebCast will cover the XML capabilities of Microsoft Data Access Components 2.5 and the various development methods available for XML integration into your data access applications. This session assumes that you have some famil |
| 31009 | Microsoft Remote Data Services (RDS) is not installed by default on the version of Internet Information Server (IIS) that comes with Windows XP Professional. When you try to access RDS, you receive the following error message: |
| 31010 | When you attempt to use versions 3.0 or later of the MSXML parser to parse XML documents that contain certain low-order non-printable ASCII characters (that is, characters below ASCII 32), you may receive the following error message: An Invalid... |
| 31011 | The Dasetup.exe program, when used with the /u switch, may not correctly roll back Microsoft Data Access Components (MDAC) to the previous version. You can verify this by using the Component Checker utility which is available at the following... |
| 31012 | Installation of Microsoft Data Access Components (MDAC) 2.6 or later on a computer that is running Windows 2000 may roll back at the very end of the installation process. The Dasetup.log file (located in the Windows directory) shows that verification... |
| 31013 | When creating an ODBC data source name (DSN) to a Microsoft Access database on a Windows Millennium Edition (Me) computer, the following error messages may result: |
| 31014 | Microsoft Data Link files provide an easy way to create or validate a Microsoft ActiveX Data Objects (ADO) connection string that uses an ODBC Driver or an OLE DB Provider to connect to a given data source. This articles discusses how to use the... |
| 31015 | When your Visual Basic project references the Microsoft ActiveX Data Objects library, if you use the Package and Deployment Wizard (PDW) to build the installation package, the Package and Deployment Wizard includes the Mdac_typ.exe file to install... |
| 31016 | When you run the PFAdmin utility from the Exchange 2000 Resource kit, you may receive the following error message: C:\Pfadmin>pfadmin Working with the Server_name server. Type 'help' for a list of commands Server_name >list |
| 31017 | Calling the ODBC API SQLTables() function on a SQL Server database name that contains an underscore (for example, my_db) may not return any of the table names contained in the database. When you use MDAC 2.7 SP1, and you call SQLTables with a... |
| 31018 | Starting with MDAC 2.7, the OLE DB Service Components support a limit on the lifetime of a pooled connection. This feature allows you to add load balanced servers on the fly. When a new server is added, the system will gradually balance |
| 31019 | OLEDBTemplate.exe demonstrates how to extract an XML stream from a SQL Server 2000 database using an XML template file. |
| 31020 | The Oledbxpath.exe sample demonstrates how to use the ATL OLE DB consumer templates to extract an XML stream for a SQL Server 2000 Databases using an XPath query. |
| 31021 | ODBC User Data Source Names (DSNs) created for a user account on Windows 2000 Terminal Server in Application Server mode may not be seen. This can result in the user being prompted with a dialog box to create a DSN each time that they establish a |
| 31022 | If a table has been created in SQL Server that contains column names of C, CA or CAS, and if a statement is prepared that uses parameters against these columns, attempting to call the SQLDescribeParam function for these parameters generates the... |
| 31023 | When running multithreaded ActiveX Data Objects (ADO) code under high stress on a multiprocessor computer, an access violation (AV) may occur when closing an ADO Recordset . Examination of the call stack at the time of the AV (with the appropriate... |
| 31024 | OLEDBSQLXML.exe demonstrates how to create an ATL OLE DB client that extracts an XML Stream from a SQL 2000 Server using a SQL XML Query. |
| 31025 | The Oledbospxml.exe sample demonstrates how to retrieve hierarchical OLE DB rowsets from an arbitrary XML document using the the Microsoft OLE DB Simple Provider (MSDAOSP) that ships with Microsoft Data Access Components (MDAC) version 2.6. |
| 31026 | DriverConf1.exe is a utility that you can use to view and record the conformance level of an ODBC driver. The value that an ODBC driver reports as its conformance level is hard coded into the ODBC driver and is not calculated at the time of a |
| 31027 | The ActualSize property of the ADODB recordset returns -1 after calling the Getchunk method to retrieve data. This problem occurs only when you use the SQLOLEDB provider that ships with MDAC 2.6 with server-side cursors. This behavior does not occur... |
| 31028 | The most recent version of the Microsoft ODBC driver for Visual FoxPro (VFP) is build 6.1.8629.1. The VFP ODBC driver is no longer included in Microsoft Data Access Components (MDAC) 2.6 or later. |
| 31029 | The Microsoft ODBC driver for SQL Server may fail to retrieve the table name with the SQLGetDescField function when a firehose cursor or a prepared statement with parameter markers is used. The following table lists the conditions and |
| 31030 | The RLockMFC.exe sample program demonstrates how to use the Microsoft Foundation Class (MFC) CDatabase and CRecordset objects with SQL Server in a Visual C++ application to pessimistically lock individual rows within a recordset while they are being... |
| 31031 | Under some circumstances, the SQL Server 2000/MDAC 2.6 RTM version of Microsoft ODBC Driver for SQL Server (2000.80.194) reuses a parameter binding that is too short. This truncates the parameter value and causes incorrect or no data to be returned.... |
| 31032 | The Microsoft ODBC Driver for Access leaks handles and threads upon opening and closing the connection. This problem is observed in drivers that ship with MDAC 2.5, 2.5 SP1, and Jet 4.0 SP5. |
| 31033 | When you update a Microsoft Excel spreadsheet through an ActiveX Data Objects (ADO) Recordset , the Excel file size grows. This behavior is most evident when you use the ADO parameters collection to make changes to the underlying spreadsheet. |
| 31034 | If you call IDBSchemaRowset::GetRowset using SQLOLEDB and a Server cursor (using DBPROP_SERVERCURSOR), you may receive an incorrect Table Catalog name. |
| 31035 | This article lists various 80004005 error messages, the most frequent causes of the error messages, and troubleshooting steps to resolve them. The 80004005 error is received by Microsoft Data Access Components (MDAC) in Active Server Pages, including... |
| 31036 | Attempting to use the Microsoft Oracle OLE DB provider to connect to Personal Oracle may result in the following error: R6025 - Pure Virtual Function Call R6025 - Pure Virtual Function Call The Microsoft Oracle OLE DB provider does not |
| 31037 | The ATLShape.exe sample demonstrates how to retrieve hierarchical data by using the MSDataShape provider. The sample reads data from either a Microsoft Access 97 database or a SQL Server 7.0 database, and writes it to an Example.out text file. Active... |
| 31038 | On a computer running Windows NT 4.0 with Microsoft Data Access Components (MDAC) 2.5 or 2.6 installed, you may receive the following error message when you attempt to open HTML Help files: You need a newer version of HHCTRL.OCX to be able to read... |
| 31039 | In Chapter 23 of the OLE DB Programmer's Reference, the section Using Schema Rowsets in OLE DB for OLAP incorrectly states that the HIERARCHIES schema rowset should contain a column with the name [ALL]_MEMBER. The name of this column should be |
| 31040 | When you attempt to open an ActiveX Data Objects (ADO) Recordset object using a file which is already open for writing as the Recordset source, the following error may occur: Run-time error '-2147024864 (80070020)': The process |
| 31041 | When attempting to connect to Microsoft SQL Server 2000, you may receive one of the following error messages: Unable to connect to server. Server msg 18, level 16, state 1. SSL security error -or- Unable to connect to server. Reason: SSL security... |
| 31042 | This article describes the features and the limitations of the current version of the Microsoft .NET Managed Provider for Oracle. |
| 31043 | When working with parameterized SQL Server stored procedures by using a data access technology such as ActiveX Data Objects (ADO), the members of the Parameters collection of the ADO Command object can be referenced by using either the name of the... |
| 31044 | OpenXML.exe demonstrates how to retrieve an ADO Recordset from an input XML document by using the OpenXML feature in SQL Server 2000. |
| 31045 | Microsoft has released a patch for SQLXML that includes updates for the issues that are described in the following Microsoft Knowledge Base articles: |
| 31046 | If you install Microsoft Data Access Components (MDAC) version 2.1, 2.5, or 2.6 on Windows NT 4.0 Terminal Server or Windows 2000 Terminal Services, sometimes the MDAC installation may fail. This problem may also occur after you use Component Checker... |
| 31047 | Installation of Microsoft Data Access Components (MDAC) version 2.5 or version 2.6 on a Microsoft Windows NT 4.0-based computer or a Microsoft Windows 2000-based computer may fail with one of the following error messages: Error Registering the OCX... |
| 31048 | When you install any software that tries to change the ODBC configuration or install ODBC components, such as Microsoft Data Access Components, service packs, or Microsoft Access, or you configure an ODBC data source through the ODBC Administrator,... |
| 31049 | If you try to use an ODBC Data Source Name (DSN) to open an ActiveX Data Objects (ADO) connection to a SQL Server database from an Active Server Pages (ASP) page, you may receive the following error message: |
| 31050 | When you attempt to create a link to an OLE DB datasource by using the Universal Data Link (UDL) wizard on the desktop, the import\export wizard, or the Data Transformation Services (DTS) designer, the available OLE DB providers are not enu |
| 31051 | Rollback of the Microsoft Data Access Components (MDAC) 2.6 Service Pack 2 (SP2) Refresh may fail under the following circumstances: Install of Microsoft SQL Server 2000 SP2 Install of MDAC 2.6 SP2 Refresh Release Rollback of MDAC by running dasetup... |
| 31052 | The OLE DB database components that are included with the Microsoft Data Access Components (MDAC) 2.7 software development kit (SDK) contain some changes from earlier versions of OLE DB to allow programmers to code to the new 64-bit platforms. This... |
| 31053 | The How to Install MDAC with a Windows Installer Merge Module white paper describes how to create a Microsoft Windows Installer merge module for Microsoft Data Access Components (MDAC). This white paper includes a sample merge module that you can... |
| 31054 | After you install Microsoft Data Access Components (MDAC) 2.5 on a Microsoft Windows 95/98 or Microsoft Windows NT 4.0 computer, a Windows Setup dialog box appears after every restart, indicating that the MDAC components are being configured. On... |
| 31055 | This article details steps you can take to correct an installation problem with Microsoft Jet 3.51. It covers troubleshooting for DAO, ActiveX Data Objects (ADO), and ODBC access methods. |
| 31056 | In a Microsoft .NET program that uses ActiveX Data Objects (ADO) through COM interop, or in a Java program that uses ADO, an access violation may occur when you call the |
| 31057 | If the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion registry key contains a registry value that is larger than 255 characters, the Microsoft Data Access Components (MDAC) Component Checker may not be able to find the files in the... |
| 31058 | The DLL Universal Problem Solver tool (DUPS.exe) is a sample that contains all the utilities documented in the January 2000 Microsoft Developer Network (MSDN) News article "The End of DLL Hell." Please review that MSDN article before readin |
| 31059 | Under some circumstances, it may be necessary or desirable to change the compatibility mode setting of version 3.70 of the SQL Server ODBC driver from SQL Server 6.5 to SQL Server 7.0. This article shows how to programmatically restore the |
| 31060 | This article describes how to set the compatibility level of version 3.70.0623 of the SQL Server ODBC driver (Sqlsrv32.dll) to SQL Server 6.5 compatibility mode. |
| 31061 | In a Microsoft Access Jet 3.5 |
| 31062 | When you call the OLEDBSimpleProviderListener::aboutToChangeCell or OLEDBSimpleProviderListener::cellChanged method, Microsoft OLE DB Simple Provider (OSP or MSDAOSP.dll) does not issue notifications. |
| 31063 | If you install Microsoft Data Access Components version 2.6 on an Exchange 2000 server, double-byte character set (DBCS) characters in the subject, location, and body part of a reply of meeting request may not display correctly when you use Microsoft... |
| 31064 | If you call the |
| 31065 | After installing Microsoft Data Access Components (MDAC) version 2.5 or later, the open and close performance of a single connection to the Microsoft ODBC for Oracle driver is noticeably slower. This impacts the performance of typical single... |
| 31066 | When you pass an ODBC canonical date literal as a parameter to a SQL Server stored procedure using the Microsoft SQL Server ODBC driver, a syntax error may be reported: [Microsoft][ODBC SQL Server Driver]Invalid time format |
| 31067 | When you use the Microsoft SQL Server ODBC driver and you use SQLSetPos to insert or update date or time values that contain the maximum allowable values for the hour, minute, second and millisecond portions (such as 1999-10-03 23:59:59:999), the... |
| 31068 | When the Microsoft Access ODBC Driver reads a date prior to 1753, the returned date is not consistent with the date actually stored in the database. When you use the Microsoft Access ODBC Driver to write dates prior to 1753, the stored dates when... |
| 31069 | When you are using the |
| 31070 | When using the Microsoft SQL Server ODBC driver (sqlsrv32.dll) in a manner that permits multiple concurrent statement handles on a single connection, a busy connection may leave cursors open in the SQL Server database with no warnings or notifications... |
| 31071 | When using an MDAC 2.1 version of the Microsoft Access ODBC driver and opening a Microsoft Access database file on a network share, an excessive amount of network packet activity occurs, even when the ODBC connection is idle. In addition, when using a... |
| 31072 | An access violation occurs in ActiveX Data Objects (ADO) if connection.Execute or command.Execute returns DB_E_CANCELLED. |
| 31073 | When using the Microsoft Oracle ODBC driver, and when using a non-U.S. platform or when the decimal separator character is not a period (.), enlistment in a distributed transaction may fail. |
| 31074 | Mtxoci.dll is a dynamic-link library (DLL) that is used internally by the Microsoft ODBC Driver for Oracle and the Microsoft OLEDB Provider for Oracle in conjunction with Microsoft Distributed Transaction Coordinator (DTC) to provide transactional... |
| 31075 | When using the OLE DB Simple Provider for Java, and when using the Recordset.Delete method, the following errors occur depending on the language that the recordset is used from: In Visual C++ Unhandled exception in program.exe (MSDAOSP.DLL):... |
| 31076 | In systems that do not have MDAC 2.1 installed on them, when you use the FoxPro ODBC ISAM Driver (named Microsoft FoxPro Driver(*.dbf) in the ODBC Administrator) for 2.5 or 2.6 tables, it allows you to view the contents of a table created in Visual... |
| 31077 | If you use the SQLConfigDataSource ODBC API call with the REPAIR_DB option on an encrypted Microsoft Access database file, the database is properly repaired, but the encryption is removed. |
| 31078 | When inserting records into a Microsoft Access database, immediately attempting to reselect them occasionally does not return all inserted records. This occurs even when the records are inserted and reselected on the same connection. The problem... |
| 31079 | Using the Microsoft Access ODBC driver, you can repair or compact a Microsoft Access database. This functionality is accessable from the ODBC Control Panel, through the ODBC Microsoft Access Setup dialog box. This repair and compact functionality... |
| 31080 | Microsoft XML (MSXML) 3.0 Service Pack 2 (SP2), or later service pack, installs only in replace mode. This release is also included with Microsoft Windows XP, Microsoft Internet Explorer 6.0, and Microsoft Data Access Components (MDAC) 2.7. Replace... |
| 31081 | This article discusses low-level ODBC API issues and MFC programming considerations for improving the performance of applications that use the Microsoft Access ODBC driver versions 2.x or above. If you are using Visual C++ 4.0 or higher, you can also... |
| 31082 | When you select NUMERIC or DECIMAL data through OLE DB and convert the data to DBTYPE_R8 (a double or float host data type for 8-byte floating-point data), the resulting values may not be correct if the locale is non-English. |
| 31083 | Service packs are the means by which Microsoft distributes bug fixes. Service packs keep a product current. Service packs include updates and may include system administration tools, drivers, and additional components, which are conveniently bundled... |
| 31084 | When you use Access 2000 Service Release 1 (SR-1) with Microsoft Jet 4.0 Service Pack 5 (SP5) to query tables linked from two separate databases on the same server, you may find that Jet does not pass the WHERE clause parameters to the ODBC data... |
| 31085 | When you update linked ODBC tables in a Microsoft Access database, an access violation occurs with the following message: The instruction at '0x1b01a333' referenced memory at '0x0000000c'. The memory could not be 'read'. This error message occurs when... |
| 31086 | The previously released download for MDAC 2.7 has been replaced with the MDAC 2.7 Refresh. Although no code changes have been made to the components in the MDAC 2.7 Refresh from MDAC 2.7, the MDAC 2.7 Refresh contains changes to the way the |
| 31087 | SQL Server 2000 was released more than a year after Access 2000 and Visual Studio 6.0. As a result, the original versions of those products do not support some of the new features of SQL Server. When you attempt to design SQL Server 2000 da |
| 31088 | When you back up a SQL Server database, a dialog box may state that there is no floppy disk in drive A, or that there is no hard disk in the removable disk drive (for example, a Zip drive). This dialog box appears on the SQL Server server, |
| 31089 | When use ActiveX Data Objects (ADO) through Active Server Pages (ASP) to connect to Microsoft SQL Server, you may receive the following error message: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver][SQL... |
| 31090 | The ActiveX Data Objects Extensions for Data Definition Language and Security (ADOX) gives ActiveX Data Objects (ADO) developers the capabilities that are present in Data Access Objects (DAO) to manipulate databases, tables, fields and other database |
| 31091 | When using the Microsoft ODBC for Oracle driver that ships with MDAC 2.5 or 2.6, establishing a connection to an Oracle database may take a long time (approximately 11 seconds) on the platforms listed above. This problem does not occur on Microsoft... |
| 31092 | When you open a report in a Microsoft Access project that uses both grouping and client-side filtering (the Filter property), the report returns no data, or you may receive the following error messages The bookmark was invalid. The bookmark |
| 31093 | After you install Microsoft Data Access Components (MDAC) 2.5, you may recieve the following error message: Error registering the OCX C:\Winnt\System32\Oleaut32.dll. Error registering the OCX C:\Winnt\System32\Oleaut32.dll. |
| 31094 | When you use an ANSI ODBC driver, the ODBC Driver Manager may incorrectly return SQL_NO_DATA_FOUND for a column that is defined as VARCHAR or CHAR and that has an empty string in it. The problem does not occur if the column contains some da |
| 31095 | When you try to open a folder by using the |
| 31096 | When you use the Microsoft Oracle OLE DB Provider (MSDAORA) for Microsoft Data Access Components (MDAC) 2.6 and 2.7 to access an Oracle fixed-length CONSTANT CHAR field, you may find that the length of the string retrieved is far greater than... |
| 31097 | Microsoft Windows XP Home and Professional Editions are shipped with the Microsoft Data Access Components (MDAC) 2.7 stack as part of the core operating system components. Although it is possible in Windows XP to replace the MDAC 2.7 stack |
| 31098 | When you install MDAC 2.1 or later, Microsoft Office 2000, or Microsoft Visual Studio 6 SP3, it upgrades the ODBC drivers for Jet from version 3.5 to version 4.0. Existing applications use the new drivers automatically and this may cause so |
| 31099 | Session pooling can provide high performance in an environment that exhibits frequent connects and disconnects from a backend database. This article describes how to get session pooling in a Visual Basic program that uses ActiveX Data Objec |
| 31100 | Certain tools, such as the SQL Server Enterprise Manager, may not display the Microsoft OLE DB Provider for OLAP Services and Microsoft OLE DB Provider for OLAP Services 8.0 in the list of providers after you upgrade to Microsoft Data Access... |
| 31101 | When you use the RDS.DataControl object to return data by using Remote Data Service (RDS), you may receive the following error message: Unexpected error. (0x80070005) Unexpected error. |
| 31102 | This article demonstrates how to call a parameterized query to an Access database using the ADO Command object and Parameters collection. This article will use VBScript samples run as Active Server Pages (ASP). |
| 31103 | The following error occurs when using RDO or ADO to update data in an Access (Jet) database: |
| 31104 | With Microsoft Data Access Components (MDAC) version 2.6 and later installed on the platforms listed above, the SQLBrowseConnect ODBC call enumerates Microsoft SQL Server 2000 instances but cannot enumerate Microsoft SQL Server 7.0 servers. |
| 31105 | During the Windows Components Update portion of Visual Studio .NET Setup, the Microsoft Data Access Components (MDAC) portion of the update fails with the following error message: digital signature error NOTE : If you are instructed to install MDAC... |
| 31106 | This article presents a step-by-step troubleshooting guide for MDAC setup issues. |
| 31107 | When you use transactional Microsoft Transaction Server (MTS)/COM+ components against Oracle databases, the components fail with the following errors in the event log: Event Source: MSDTC Event Category: XATM Event ID: 53286 Date: 10/2/2000 Time:... |
| 31109 | When you enable a SQL Server application role on a Microsoft ActiveX Data Objects (ADO) connection to SQL Server, you may receive the following error message when you connect to SQL Server 7.0: sp_setapprole was not invoked correctly. Refer to the |
| 31110 | SQLDescribeCol returns an incorrect column size for a complex union query that contains parameters and a WHERE clause. |
| 31111 | This article discusses the use of ActiveX Objects (ADO) with Microsoft Excel spreadsheets as a datasource. The article also highlights syntax issues and limitations specific to Excel. This article does not discuss OLAP or PivotTable technologies or |
| 31112 | Under the following conditions: User on computer A (either Windows NT or Windows 9x) is running SQL Enterprise Manager or Query Analyzer, managing a SQL Server on a Windows NT computer B. The user creates a Linked Server, specifying a |
| 31113 | This article provides a list of some useful articles pertaining to Microsoft Data Access Components (MDAC). MDAC articles are not limited to this list; for a comprehensive list, search the Microsoft Knowledge Base at http://support.microsoft.com with... |
| 31114 | This article describes two different ways to check which version of Microsoft Data Access Components (MDAC) is installed on a system: |
| 31115 | The |
| 31116 | Microsoft does not provide a stand-alone installation package for the ODBC components and drivers. ODBC can only be installed as part of the Microsoft Data Access Components (MDAC). |
| 31117 | The ActiveX Data Objects (ADO) Recordset object has methods and properties that allow you to use it to perform FoxPro-style record navigation. |
| 31118 | When you call managed or unmanaged transactional COM+ components from ASP.NET, one or more of the following problems may occur in your application: Access violations Memory leaks Handle leaks Deadlocks Poor performance |
| 31119 | This step-by-step article describes how use Microsoft Visual C++ to call the ADO |
| 31120 | Either of the following errors occur when you execute an Active Server Pages (ASP) page that is making subsequent stored procedure calls: |
| 31121 | This article demonstrates how to use the ActiveX Data Objects (ADO) OpenSchema method from Visual C++ using the #import feature. OpenSchema is a method of ADO the Connection object that obtains database schema information from the OLEDB pro |
| 31122 | This article describes how to use Active Server Pages (ASP) code to populate an ActiveX TreeView control. The technique shown here leverages ASP's ability to dynamically build a VBScript function to populate a client-side ActiveX control, b |
| 31123 | The following error may occur when you use DEConnection in a Visual Basic COM object running under ASP: Run-time error '-2147467259 (80004005)': [Microsoft][ODBC DriverManager] Only SQL_DRIVER_NOPROMPT is allowed when connection pooling is enabled |
| 31124 | Using stored procedures on a SQL Server and the Visual FoxPro SQLEXEC() function, it is possible to administer database users and groups from within a Visual FoxPro program. The following sample code demonstrates how to accomplish this. |
| 31125 | When using integrated security with SQL Server, the presence or absence of a login ID determines if a user is uniquely known within SQL Server or is instead mapped to a default account, if one exists. If no default account and no login ID e |
| 31126 | The Execute method of the ActiveX Data Objects (ADO) Command object passes by reference an integer value that you can use to retrieve the number of records affected by a SQL UPDATE command. |
| 31127 | You can configure ODBC (Open Database Connectivity) data source names programmatically. This gives you flexibility to export data without forcing the user to explicitly use the ODBC Administrator or other programs to specify the names of da |
| 31128 | After installing or upgrading ODBC files, you receive one of the following error messages: |
| 31129 | This article lists the different versions of the ODBC Driver Manager and the SQL Server driver shipped. |
| 31130 | When you attempt to set an ActiveX Data Objects (ADO) Data Control's Recordset object to a previously dimensioned ADO Recordset the following error is returned: |
| 31131 | The DataReport is a powerful tool and it's easy to build complex reports by dragging and dropping fields out of the DataEnvironment window. However, there are times when you may want to bind the DataReport directly to an ActiveX Data Object |
| 31132 | In Data Environment, when a hierarchical recordset is used, and the parent/child/grandchild recordsets are bound, the expected behavior is for all the child/grandchild recordsets to "stay in sync" with the parent. However, when record in th |
| 31133 | This article explains the various settings required to launch custom business objects over HTTP or the Distributed Component Object Model (DCOM) using Remote Data Services (RDS). |
| 31134 | When you attempt to use the ActiveX Data Objects (ADO) Find method to search by multiple criteria, or in other words you use AND, the following error occurs: |
| 31135 | An ODBC Driver, which is written to conform to the ODBC 3.0 Specification, must support the SQL_C_NUMERIC datatype. If the driver returns 3.0 on a call to the SQLGetInfo function (using SQL_DRIVER_ODBC_VER), but does not support the SQL_C_N |
| 31136 | If a Connection's CommandTimeout property is set to some value and a Command object is associated to that Connection, the Command object does not pickup the Connection's CommandTimeout setting. Instead, the Command object's CommandTimeout i |
| 31137 | When using a SHAPE statement to retrieve parent and child records, the SHAPE provider pulls down all child records regardless of whether there is a matching parent record. |
| 31138 | The purpose of this article is to help you understand how the Visual Basic 6.0 Package and Deployment Wizard (PDW) distributes the Microsoft Data Access Components (MDAC) in order to allow you to control which version of MDAC is distributed with your... |
| 31139 | When inserting data into a Bit (Yes/No) field in a Microsoft Access database via the Microsoft Access ODBC driver, the resulting data in the bit field is always False, even when a value of True was specified. This behavior occurs when using the... |
| 31140 | While using ADO to access a Sybase database table using an ADO server-side cursor (adUseServer), the last trailing zero in a numeric field is truncated. This happens while accessing the Sybase database through the Microsoft OLE DB provider |
| 31141 | When calling a SQL Server stored procedure that uses Exec('string') syntax, you may get an error returned to the calling client if you are referencing values using double quotes. The error that is returned to the calling client is: |
| 31142 | This article demonstrates how to programmatically retrieve an XML data stream from a SQL Server 2000 mapping schema by using an XPath query. The scope operates in a client/server (2-tier) model. This sample also allows you to test XPath queries... |
| 31143 | When you use the MSXML parser in a high-stress environment such as Microsoft Internet Information Services (IIS), a bottleneck may occur while the MSXML parser performs garbage collection, such as around the msxml3!ShareMutex__SleepWaitingForLock... |
| 31144 | When the Remote Data Service (RDS) for ActiveX Data Objects (ADO) is used with an OLE DB provider that was built by using the OLE DB Simple Provider (OSP) Toolkit, the following error message may occur: |
| 31145 | When you attempt to connect to a SQL Server through TCP/IP on a Windows 98 client, the following error message can occur: Assertion failed! Program: C:\WINDOWS\RUNDLL32.EXE File: ../src/sqlsspi.c Line: 120 Expression: Count For information on how your... |
| 31146 | With #import, it is possible to generate classes that encapsulate the typelib of database API's, such as ActiveX Data Objects (ADO), within a windows application. For example: |
| 31147 | When you install the Microsoft Data Access Components (MDAC) on a system running Windows NT, if you are logged on as a user without Administrator privileges, you see an error such as the following: You must have administrative privileges to install or... |
| 31148 | When using Query-Based Updates against Oracle databases within ActiveX Data Objects (ADO), such as Visual InterDev's Data Form Wizard, only forward-only cursors work without error. If you use Static, Keyset, or Dynamic cursors and the ADO Update... |
| 31149 | ADOEvts.exe is a sample that demonstrates how to capture events from Microsoft Active Data Objects (ADO). The ADO events in this sample were added with ADO version 2.0. |
| 31150 | After saving and closing a remote view with a date criteria in the Open Database Connectivity (ODBC) Date Format, the View Designer does not read the criteria correctly. For example: |
| 31151 | The main purpose of the ActiveX Data Objects (ADO) Command object is to allow the execution of stored procedures and parameterized commands against a data provider. |
| 31152 | When you create a Recordset object without an active command, the recordset remains empty until it is associated with one. Therefore, it is possible to create a Recordset object at any point in a procedure, but not populate it until necessa |
| 31153 | After issuing a Modify View command, the following message displays: |
| 31154 | SQL Server 7.0 allows the addition of external data sources as linked servers. This feature provides access to distributed, heterogeneous queries against OLE DB data sources. When connecting to SQL Server, a cursor listing available tables |
| 31155 | When you use the AppWizard to create a CRecordset class using the ODBC Text Driver, your project will compile. However, when you try to open the recordset, you will get the following error message: |
| 31156 | AdoChunk.exe is a sample that demonstrates using the GetChunk and AppendChunk methods with Visual C++ version 5.0. The sample also demonstrates the use of recordset navigation functions. |
| 31157 | Microsoft Data Access Components (MDAC) version 2. x has increased inter-dependencies compared to previous releases. This poses some implications for redistribution, especially for Remote Data Service (RDS) Client applications. |
| 31158 | Mdaccon.exe is a sample that that demonstrates the use of ODBC Driver and OLE DB Provider connection strings. Four separate projects, one each in C++, Visual Basic for Applications, and Java, as well as a C++ OLE DB Consumer Application, de |
| 31159 | When attempting an ActiveX Data Objects (ADO)/ Remote Data Services (RDS) update, using the OLEDB provider for ODBC (MSDASQL) with a third party ODBC driver, you may receive an error. |
| 31160 | An attempt to update a large (64K or greater) memo field in a client-side recordset using the Jet 3.51 OLE DB provider results in one of the following errors: Errors occurred. Run-time error '-2147217887(80040e21)': -or- Run-time error... |
| 31161 | The Microsoft Visual Basic sample in this article demonstrates how to return multiple ActiveX Data Objects (ADO) Recordsets from a Microsoft SQL Server stored procedure. The code also demonstrates how to extract the column names and values |
| 31162 | When using the Advworks data source name (DSN) that installs with the Microsoft Data Access Components (MDAC) files, the following error may occur: Run-time error -2147467259(80004005) General Error Unable to Open registry key DriverID. |
| 31163 | When using the Microsoft Oracle ODBC driver (Msorcl32.dll) provided with the Microsoft Data Access Components (MDAC) 1.5x and more than 64K of data is returned to the client computer in a scrollable or keyset driven recordset, temporary files may be... |
| 31164 | When you call the AddNew method, and then call the Update method of a Recordset, the following error is returned: |
| 31165 | The following error message occurs when trying to connect to SQL Server using ActiveX Data Objects (ADO): |
| 31166 | If you try to run the Microsoft Data Access Components setup on a Windows 95 computer, you get a warning indicating that you need DCOM95 to install MDAC. |
| 31167 | When you try to use the Query Designer against the MS Shape Provider in the Data Environment, the following error message is returned: Query Designer encountered a ADODB.Properties error: Query Designer encountered a ADODB.Properties error: Query... |
| 31168 | Xslatezp.exe is a self-extracting executable that performs data translations between Microsoft Access, Microsoft FoxPro, Microsoft SQL Server, and Microsoft Excel. This article demonstrates translation of data from one database format to another using... |
| 31169 | When submitting changes using the SubmitChanges of the RDS.DataControl or the RDSServer.DataFactory the user may see the following error message: [Microsoft][ODBC Microsoft Access 97 Driver] The Microsoft Jet database engine cannot open the file... |
| 31170 | Microsoft Data Access Components (MDAC) versions 1.5 and later include ODBC, OLE DB, ActiveX Data Objects (ADO), and the Remote Data Services (RDS). These components were tested with Windows 9x and Windows NT 4.0 (Service Pack 3) and later. |
| 31171 | When you filter a recordset for a character field that contains more than one single quotation mark, for instance CompanyName = O'Riley's Pub, one of the following error messages is displayed: |
| 31172 | The Microsoft Data Access Components (MDAC) version 2.1 installs the Microsoft Jet 4.0 database engine. The Microsoft Jet database engine is used by the Microsoft Access ODBC Driver, the Microsoft Jet OLE DB Provider, and the Microsoft Data Access... |
| 31173 | In some cases, when running queries from Microsoft Access or any application that uses Jet/VBA, like Data Access Objects (DAO), that involve an ODBC timestamp or SQL datetime data with the fractional portion of the timestamp having a higher precision... |
| 31174 | This article lists the version numbers of the Microsoft XML parser (Msxml.dll Msxml2.dll, Msxml3.dll, and Msxml4.dll) and the Microsoft products that include this component. |
| 31175 | This sample in this article demonstrates how to retrieve an XML document from SQL Server 2000 by using a template file that contains parameters. More specifically, a query is issued against SQL Server 2000 by using an ADO 2.6 command strea |
| 31176 | When opening a connection in Active Server Pages (ASP) code to SQL Server on a separate computer from the Web server, one of these similar error messages may appear: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL... |
| 31177 |
|
| 31178 | A Microsoft Visual C++ database project that uses the Microsoft Access 97 (Jet 3.5) ODBC Driver has a noticeable drop in performance compared to similar projects that use the Microsoft Access 95 (Jet 3.0) ODBC Driver. |
| 31179 | This article covers some of the most frequently asked questions about ODBC connection pooling. |
| 31180 | Neither Open Database Connectivity (ODBC), nor Microsoft OLE DB Provider, supports Nested Transactions. ActiveX Data Objects (ADO) supports the feature, but only if the underlying provider exposes it. Currently only the Jet OLE DB provider supports... |
| 31181 | Active Server Pages (ASP) and ActiveX Data Objects (ADO), Internet Information and Microsoft Windows NT Server version 4.0, connections to an ORACLE/Sybase database on an UNIX system may fail with an ASP Error 0115. |
| 31182 | When you try to open a connection to a Microsoft SQL Server database from an Active Server Pages (ASP) page, you get the following error: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server... |
| 31183 | When you run an ADODB command stream and specify SQL SELECT with the FOR XML AUTO clause, an XML document stream is fetched from SQL Server, sent to the response object, and piped to the client. Properties to be set for the properties of the... |
| 31184 | When transactional COM+/MTS components call Oracle external stored procedures, no rows are returned the first time, and the following error is returned on subsequent method calls: -2147467259 Microsoft OLE DB Provider for ODBC Drivers[Microsoft][ODBC... |
| 31185 | When you open an ActiveX Data Objects (ADO) connection from a transactional component in COM+, Microsoft Transaction Server (MTS), or any transactional Active Server Pages (ASP) page, you may receive the following error message if you use Microsoft... |
| 31186 | If a Visual FoxPro table has an index tag that calls a User Defined Function or a FoxPro function like DELETED() or RECNO(), the table cannot be imported or linked from Microsoft Access. |
| 31187 | When you perform a numeric comparison or calculation on an adNumeric (131) field type using VBScript, the following errors may be returned: Microsoft VBScript runtime error '800a000d' Type mismatch Microsoft VBScript runtime error '800a01ca' Variable... |
| 31188 | If you install Microsoft Data Access Components (MDAC) 2.7 after you have installed MDAC 2.6 Service Pack 2, you may receive the following error message: |
| 31189 | The Visual Basic 6.0 documentation incorrectly states that Visual Basic 6.0 can build an OLE DB provider. |
| 31190 | When you use a Report Control that is bound to a Visual Basic Data Environment command object and perform a GroupBy, you receive the following error: |
| 31191 | Applications that use the Microsoft Jet Database Engine can prevent a computer that supports the Advanced Power Management (APM) or the Advanced Configuration and Power Interface (ACPI) technologies from going into Standby mode. |
| 31192 | Originally, ADOR was designed to be a standalone component. However, as ADO has evolved in design and use, this is no longer ADOR's purpose. ADOR is now only a sub to the MSADO15.DLL and exists only to maintain backward compatibility. |
| 31193 | Running a Visual Basic application using the Microsoft RDS Data Factory to access Index Server 2.0 can generate the following errors: Run-time error '-2147217887 80040e21': Errors Occurred. |
| 31194 | The following table summarizes the support for ITransactionLocal and ITransactionJoin interfaces for current versions of OLEDB providers supplied or produced by Microsoft. This information is useful when you are working with an OLEDB provid |
| 31195 | Microsoft Remote Data Service for ADO (RDS) fails with different error messages when used in conjunction with some firewalls and proxy servers. |
| 31196 | This article presents a list of all the files installed by MDAC 2.0 SP2. MDAC 2.0 SP2 (Mdac_typ.exe) can be downloaded from http://msdn.microsoft.com/dataaccess . All the following locations of files are given as they were installed on Windows NT. For... |
| 31197 | If you run an ADODB command stream and specify SQL SELECT with the FOR XML AUTO clause, an XML document stream is fetched from SQL Server and displayed in the Visual Basic Intermediate window. You must set the following properties for the Properties... |
| 31198 | When installing Microsoft Data Access Components (MDAC) 2.6 RTM (version 2.60.6526.3) on computers that have 32 processors, the following error may occur when Msxml2.dll is registered: A dynamic link library (DLL) initialization routine failed This... |
| 31199 | Some OLE DB providers, such as Microsoft's Oracle OLE DB Provider, do not support updating via IRowsetChange, although they do support updating via SQL UPDATE statements. In this case, the OLE DB Cursor Engine service can be used to allow the provider... |
| 31200 | When you use Microsoft Internet Explorer to open an XML file that has no encoding specified and that contains characters with high ASCII-codes, and your computer is running Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium... |
| 31201 | OLE DB specification doesn't provide interfaces to compact or repair databases. However, the OLE DB Provider for Microsoft Jet version 4.0 exposes this functionality through a custom interface: IJetCompact (TDataSource cotype). IJetCompact is defined... |
| 31202 | This article describes the limitations of the current version of Microsoft ODBC Driver and OLE DB Provider for Oracle. |
| 31203 | When you add an ODBC connection to Sybase 11x and the catalog name is specified in the connection string for the Microsoft OLE DB Provider for ODBC Drivers, this error occurs: |
| 31204 | When trying to connect to an Access .mdb file, an ODBC error is returned stating Disk or Network Error. The Microsoft OLE DB Provider for the Microsoft Jet database engine may also return an Unspecified error (error code = 0x80004005) message. The... |
| 31205 | You can use IRowsetIndex::Seek() to quickly search an indexed column. The Jet 4.0 OLE DB provider natively supports the IRowsetIndex interface, while the Microsoft SQL Server OLE DB Provider, Microsoft OLE DB Provider for Oracle, and other Microsoft... |
| 31206 | The Microsoft Access ODBC Driver does not support multiple result sets of native Access tables. Calling SQLGetInfo( hdbc, SQL_MULT_RESULT_SET, ... ) returns an 'N' signifying the driver does not support multiple result sets. This means an application... |
| 31207 | This article demonstrates how to programmatically use Data Links feature of the Microsoft Data Access Components in order to generate a connection string at run-time. |
| 31208 | Negative values inserted into numeric fields of remote views of SQL Server tables are rounded up by 0.01. |
| 31209 | When you use the Jet OLE DB Provider version 4.0, an application may fail with the following error message: Run-Time Error -2147467259 (80004005) Method 'Open' of Object '_Recordset' Failed. This error occurs when trying to issue certain queries to... |
| 31210 | If a WITH statement is used to store an empty string value to one field and an uninitialized string to the very next field, an error will occur when using the Microsoft OLE DB Provider for Jet 3.51 or 4.00 that shipped with MDAC versions prior to 2.5.... |
| 31211 | When you set or check the default column values for any column in a table that is contained in an Access 2000 database, the default values for the column are cleared. |
| 31212 | SmAlert.exe is a sample that extends the usefulness of the PerfMon tool by storing PerfMon alerts in a database. |
| 31213 | When you insert a number of records into a table in a Microsoft Access database, you may want any records that duplicate existing records to be ignored with no error or warning message, and you may want only unique new values to be inserted. Data... |
| 31214 | This article shows by example how to extract the bitmap photos in the Microsoft Access 97 Nwind.mdb database, and view them from a Web browser using Active Server Pages (ASP). In order to accomplish this task, an ActiveX DLL must be created that... |
| 31215 | This article outlines the different Microsoft Data Access Component (MDAC) versions available and the products that install them. |
| 31216 | When you execute a statement that was prepared with the SQL_ATTR_NOSCAN attribute, you may receive an access violation (AV) as follows: Unhandled exception in appname.exe (SQLSRV32.DLL): 0xC0000005: Access Violation. |
| 31217 | Using the Microsoft OLEDB Provider for SQL Server (SQLOLEDB) that comes with Microsoft Data Access Components (MDAC) version 2.6 or 2.6 SP1, when you set the value of the SSPROP_ENABLEFASTLOAD property to true in the SQLSERVERDATASOURCE property set,... |
| 31218 | When you use Microsoft OLE DB Provider for Oracle (MSDAORA) to run a stored procedure that takes parameters of 30 characters in length, you receive the following error message: |
| 31219 | When using ActiveX Data Objects (ADO) against certain OLE DB providers, you may find that recordset fields that should be NULL do not test for NULL correctly either by checking the VARIANT.vt value for VT_NULL (in Microsoft Visual C++) or b |