| 31221 | Error message when you use Microsoft ActiveX Data Objects in an application after you install security update MS06-014 on a Windows 98-based computer or on a Windows Millennium Edition-based computer: ActiveX component can't create object |
| 31222 | You receive multiple error messages if ProClarity Web Professional is not set to use the same language as the client operating system |
| 31223 | The COM+ process stops responding after a Visual Basic application uses the Microsoft Oracle ODBC driver to connect to an Oracle database server that is hosted on a Windows Server 2003-based computer or on a Windows XP-based computer |
| 31224 | Incorrect data is returned when you change the binding order of two similarly-named output parameters in an application that uses the ODBC driver in Windows XP Service Pack 2 |
| 31225 | The IRow::GetColumns function of the Exchange OLE DB provider unexpectedly returns error code 0x80010105 on a server that is running a 64-bit version of Windows Server 2003 Service Pack 1 |
| 31226 | You may receive an error message when you use a localized ODBC driver in your application on a Windows Server 2003-based computer or on a Windows XP SP2-based computer |
| 31227 | Installation requirements for the MDAC update that is described in Microsoft Security Bulletin MS06-014 |
| 31228 | MS06-014: Vulnerability in Microsoft Data Access Components (MDAC) function could allow code execution |
| 31229 | 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 |
| 31230 | You are prompted to send an error report to Microsoft when you try to apply a MDAC software update |
| 31231 | You are prompted to continue the software removal process when you use Spuinst.exe and the /passive switch to remove an MDAC update |
| 31232 | You may be prompted to send an error report to Microsoft if you do not restart the computer between MDAC updates |
| 31233 | An ADO-based application may unexpectedly exit when the application makes an asynchronous call to the Connection.Execute method on a computer that is running Data Access Components 2.8 |
| 31234 | An access violation may occur when you declare a global type recordset variable and you try to close the recordset in Microsoft Data Access Components (MDAC) 2.8 Service Pack 1 |
| 31235 | An ADO application crashes after you install Windows Server 2003 SP1 or Windows XP SP2 |
| 31236 | International settings in SET POINT TO and SET SEPARATOR TO cause the following error to occur in the SQL Server Upsizing Wizard: To upsize to SQL Server 6.x, please install a SQL Server ODBC driver version 2.05 or later This error does not occur... |
| 31237 | An application intermittently crashes on exit and an error similar to the following appears: application caused an invalid page fault in module KERNEL32.DLL at 0137:bff9a07c. This behavior occurs when the application is using the MFC DAO... |
| 31238 | Release Manifest for MDAC 2.5 SP2 (2.52.6019.2) |
| 31239 | Unhandled exceptions occur in an application when the application uses the SQLGetPrivateProfileString function and the ODBC_BOTH_DSN configuration mode in Microsoft Data Access Components (MDAC) 2.8 |
| 31240 | Description of the type mapping of the new SQL Server 2005 data types in Microsoft Data Access Components |
| 31241 | A memory leak may occur when you use the Advanced Data Tablegram persistence mechanism to persist a hierarchical recordset to a Stream object in a Microsoft Data Access Components 2.8 application |
| 31242 | You notice a small memory leak when a direct or indirect call to the WrapDSOandSession method of ADO Connection object is made and the MSDataShape provider is not used in MDAC 2.8 |
| 31243 | Release manifest for MDAC 2.8 Service Pack 1 (2.81.1117.6) |
| 31244 | Explains that the installation of MDAC 2.8 fails when you try to install it from a Windows Installer package on a computer that is running Windows 2000. Explains that you have to modify the Windows Installer package to work around this behavior. |
| 31245 | Explains that SQL Server ODBC Drivers throws Error with Connection Pooling |
| 31246 | Fixes the problem where the server name IP resolution fails when you connect a client computer to a computer that is runnin SQL Server 2000. Provides a workaround for this problem. |
| 31247 | Fixes a problem that causes an access violation and BCP to fail when you try to import data that has a mismatch field for a data column. |
| 31248 | Fixes a problem with the bcp utility. The bcp utility may not import data from a text file if the computer has MDAC 2.8 installed, if the text file contains DCBS characters, and the text file is larger than 32 MB. |
| 31249 | Fixes the error that is caused when you try to insert or to update data in a multi-table view by using a server side cursor over an OLEDB connection. Occurs even if an INSTEAD OF trigger is defined on the view. Contains a hotfix to resolve the... |
| 31250 | Describes a fix for a problem that occurs when you use the OLE DB Provider for SQL Server to modify a row on a table. If the table contains a trigger, and the trigger contains a FETCH command, you receive an error message. |
| 31252 | Explains the cause for the deadlock that occurs in a multi-threaded application when the ODBC32.dll file tries to load an MFC extension DLL such as the ODBCCR32.dll file. To resolve this, install Microsoft Windows XP Service Pack 2. |
| 31253 | Fixes a problem that causes an access violation to occur when the SQLOLEDB provider tries to access the sqlxmlx.dll file. Provides a link to the service pack that fixes this problem. |
| 31254 | The Microsoft Data Access Components (MDAC) 2.7 redistributable installer contains files for communicating with the database by using Banyan Virtual Integrated Network Service (VINES) and AppleTalk protocols. However, the MDAC 2.8 redistributable... |
| 31255 | This article discusses the Handunsf.reg file, which is removed from MDAC 2.8 Redist Setup Program. By running this Handunsf.reg file, you can change the default secure setting of the WWW Publishing Server and make the server to run in Unsafe Mode.... |
| 31256 | Lists the bugs that are fixed in MDAC 2.8 SP1. |
| 31257 | Fixes the error message that you receive when you use the OLE DB Provider for ODBC that returns SQL_CB_DELETE when you call the SQLGetInfo function with the SQL_CURSOR_COMMIT_BEHAVIOR attribute. |
| 31258 | Describes a problem that occurs when you call the GetParameterInfo method with the command text set to an ODBC call escape sequence in MDAC 2.8. |
| 31259 | Discusses a problem where MDAC files do not install correctly during an upgrade to Windows Server 2003. You receive error messages after the upgrade. |
| 31260 | Fixes a problem that occurs when you run a query against a local view that is referencing a remote view through a Microsoft OLE DB Provider for SQL Server linked server. The query returns a text field, an ntext field, or an image field. |
| 31261 | Explains that you receive an error message when you try to configure a Text DSN by using the ODBC Data Source Administrator tool on a computer that is running Windows XP SP2. Provides a list of files that are updated in the hotfix. |
| 31262 | 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. |
| 31263 | Describes that DTS packages fail with an unspecified error from Sqloledb.dll. This problem occurs after you apply Windows XP Service Pack 2. |
| 31264 | Describes a problem that occurs after you use the Snapshot Agent to perform snapshot replication, merge replication, or transactional replication. When you use the Distribution Agent or the Merge Agent you receive an error message. |
| 31265 | Contains a list of all the hotfixes that are available for MDAC 2.8. |
| 31266 | Fixes a problem that occurs when you set the rowset size to a value that is larger than 1. When the rowset size is larger than 1, lock time-out errors may not be returned when you call SQLFetch, and a deadlock condition occurs. |
| 31267 | Describes the release strategy for Microsoft Data Access Components (MDAC). After MDAC 2.8 SP1, MDAC will not be available as a stand-alone redistributable package. |
| 31268 | Discusses an access violation that may occur when a program calls the UpdateBatch method of an ADO Recordset object by using the OLE DB Provider for ODBC in Data Access Components. |
| 31269 | Describes the MDAC hotfix installer tool that is used to install hotfixes and security updates on a 32-bit operating system. |
| 31270 | Describes a problem that occurs when programs that use the SQL Server ODBC driver to asynchronously run a SQL Server stored procedure may stop responding. Includes a hotfix to resolve the problem. |
| 31272 | Describes where you can get the latest service pack for MDAC 2.8 |
| 31273 | Fixes the problem of establishing a new connection in a SQL Server when the transactional component connects to the SQL Server. The transactional component can reuse the nontransactional connection in OLE DB resource pooling. |
| 31274 | Fixes the problem when your application use the Microsoft SQL Server ODBC driver to run a lengthy and asynchronous stored procedures and the results are processed by SQL server and again sent back to the client. |
| 31275 | 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. |
| 31276 | 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. |
| 31277 | 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. |
| 31278 | Explains that the functionality of the GuessTheColDef connection string attribute of the Microsoft ODBC driver for Oracle is same as the SQLDescribeCol always returns a value for precision check box in the Data Sources dialog box. |
| 31279 | Describes a problem that occurs when you try to insert more than 65,535 records in a SQL Server table by using the SQLBulkOperations function. Includes a workaround for the problem. |
| 31280 | 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. |
| 31281 | 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. |
| 31282 | Provides answers to Frequently Asked Questions (FAQs) regarding the setup and installation of MDAC 2.6. |
| 31283 | 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. |
| 31284 | Fixes the performance of the SET FMTONLY Transact-SQL query hint. |
| 31285 | 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. |
| 31286 | 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... |
| 31287 | 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. |
| 31288 | 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. |
| 31289 | Provides the information about release manifest for MDAC 2.7 Refresh (2.70.9001.0) |
| 31290 | 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. |
| 31291 | 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. |
| 31292 | 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... |
| 31293 | 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... |
| 31294 | Provides a fix for a problem that occurs when a long query string is used for a hierarchical ADO Recordset with MDAC 2.8. |
| 31295 | 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... |
| 31296 | 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... |
| 31297 | 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. |
| 31298 | OLEDB provider gets access violation with the DBPROMPT_PROMPT property. |
| 31299 | 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... |
| 31300 | 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... |
| 31301 | When executing a stored procedure with multiple queries (SELECTs, INSERTs and UPDATEs), the ActiveX Data Objects (ADO) errors collection appears not to be populated after an error occurs in the stored procedure. The stored procedure might also not... |
| 31302 | You cannot create out-of-process providers with Microsoft Data Access (MDAC) OLE DB components. |
| 31303 | 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... |
| 31304 | 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. |
| 31305 | 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... |
| 31306 | 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... |
| 31307 | 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... |
| 31308 | This article presents a step-by-step troubleshooting guide for MDAC setup issues. |
| 31309 | 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... |
| 31310 | 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... |
| 31311 | 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. |
| 31312 | 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... |
| 31313 | 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:... |
| 31314 | 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... |
| 31315 | 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... |
| 31316 | 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... |
| 31317 | 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... |
| 31318 | 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... |
| 31319 | 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... |
| 31320 | 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. |
| 31321 | 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. |
| 31322 | 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:... |
| 31323 | 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... |
| 31324 | 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... |
| 31325 | 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... |
| 31326 | 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). |
| 31327 | 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... |
| 31328 | 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. |
| 31329 | 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:... |
| 31330 | 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. |
| 31331 | 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... |
| 31332 | 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... |
| 31333 | 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... |
| 31334 | 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. |
| 31335 | 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. |
| 31336 | 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 (... |
| 31337 | 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-... |
| 31338 | 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). |
| 31339 | 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... |
| 31340 | 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. |
| 31341 | 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... |
| 31342 | You might experience slow performance or high CPU utilization, or the system may stop responding. If you attach a debugger to the process, or you load a user dump file in a debugger with correct symbol files setup, you might experience high critical... |
| 31343 | 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. |
| 31344 | 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... |
| 31345 | 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... |
| 31346 | 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... |
| 31347 | 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:... |
| 31348 | 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 |
| 31349 | 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... |
| 31350 | 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. |
| 31351 | 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. |
| 31352 | When you use Microsoft ActiveX Data Objects (ADO) to retrieve data, an access violation occurs in Oledb32.dll. |
| 31353 | 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... |
| 31354 | 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... |
| 31355 | 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... |
| 31356 | 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... |
| 31357 | 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... |
| 31358 | When you attempt to run simple ActiveX Data Objects (ADO) code in an application, the following error can occur: Method '~' of Object '~' Failed |
| 31359 | 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. |
| 31360 | 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... |
| 31361 | When you profile an application that uses the SQL Server ODBC driver and calls the ODBC functions SQLPrepare , SQLExecute , and SQLExecDirect , you may observe an excessive amount of CPU time in the iswctype C run-time function. |
| 31362 | 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... |
| 31363 | 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. |
| 31364 | This article lists the different versions of the ODBC Driver Manager and the SQL Server driver shipped. |
| 31365 | 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. |
| 31366 | When you open a server-side cursor and call the SQLTables or SQLTablesW function against a Microsoft SQL Server database whose name contains an underscore (_), the SQL Server ODBC driver generates SQL_SUCCESS_WITH_INFO with the following message:... |
| 31367 | 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... |
| 31368 | 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... |
| 31369 | When you use server-side Keyset cursors with the OLE DB Provider for ODBC shipping with MDAC 2.0, a hash table is created, which is used to hold bookmarks for each row in the rowset, and the provider allocates 64 kilobytes to the table by default. |
| 31370 | 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... |
| 31371 | 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... |
| 31372 | 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... |
| 31373 | 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... |
| 31374 | 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... |
| 31375 | 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. |
| 31376 | 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... |
| 31377 | 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. |
| 31378 | 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... |
| 31379 | 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... |
| 31380 | This article lists the locations of the available release manifests for Microsoft Data Access Components (MDAC) products. |
| 31381 | 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,... |
| 31382 | 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... |
| 31383 | 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... |
| 31384 | 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... |
| 31385 | 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. |
| 31386 | 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... |
| 31387 | 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... |
| 31388 | 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. |
| 31389 | 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. |
| 31390 | 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,... |
| 31391 | 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... |
| 31392 | 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... |
| 31393 | 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... |
| 31394 | 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... |
| 31395 | 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... |
| 31396 | 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... |
| 31397 | This article describes the limitations of the current version of Microsoft ODBC Driver and OLE DB Provider for Oracle. |
| 31398 | 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. |
| 31399 | This article outlines the different Microsoft Data Access Component (MDAC) versions available and the products that install them. |
| 31400 | 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... |
| 31401 | 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... |
| 31402 | 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... |
| 31403 | 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... |
| 31404 | 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... |
| 31405 | Invoking Parameters.Refresh may incorrectly return the wrong direction value for some parameters in the Parameters collection. When attempting to execute the Command Object for a parameterized query you may encounter thefollowing error message:... |
| 31406 | 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... |
| 31407 | 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... |
| 31408 | This article describes the features and the limitations of the current version of the Microsoft .NET Managed Provider for Oracle. |
| 31409 | 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... |
| 31410 | 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... |
| 31411 | 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... |
| 31412 | 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-... |
| 31413 | 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... |
| 31414 | 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... |
| 31415 | When updating an ActiveX Data Objects (ADO) recordset, an error occurs if the recordset, based on a SHAPE command, joins two tables where the primary key of one table has the same name as a column name of the other table. The following error appears:... |
| 31416 | When you increase the depth of the child recordset in a SHAPE command object by adding large number of recordsets, your application may quit unexpectedly. |
| 31417 | 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... |
| 31418 | 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... |
| 31419 | When you open two recordsets with the Msdatashape provider, the second recordset has the incorrect number of records. |
| 31420 | When you use Remote Views with the SQL Server ODBC Driver (Sqlsrv32.dll version 2.65.0252, 3.50.0303, or 3.50.0311) to send numeric data containing decimal values to SQL Server tables, incorrect decimal values may be inserted into SQL Server tables. |
| 31421 | 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... |
| 31422 | This article discusses some of the main ODBC Administrator changes that are introduced with Microsoft Data Access Components (MDAC) 2.8. By default, all the trace logs in MDAC 2.8 are stored in the secured temp folder in the following location:... |
| 31423 | 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... |
| 31424 | 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... |
| 31425 | 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... |
| 31426 | 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... |
| 31427 | 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... |
| 31428 | 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... |
| 31429 | 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. |
| 31430 | 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... |
| 31431 | When using the Remote View Wizard to connect to a Visual FoxPro table, you receive the following error in the final step of the wizard: Connectivity error:[Microsoft][ODBC Visual FoxPro Driver]Command contains unrecognized phrase/keyword. When you... |
| 31432 | When using the Filter property in ActiveX Data Objects (AD0) version 1.5 in conjunction with the AbsolutePaging and PageSize properties, the recordset returned from the database displays the same record or records on multiple pages. This scenario is... |
| 31433 | 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. |
| 31434 | 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 |
| 31435 | 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 |
| 31436 | 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 |
| 31437 | 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: |
| 31438 | 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 |
| 31439 | 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 |
| 31440 | When you use the ODBC API function |
| 31441 | When running ODBC applications on Microsoft Windows 2000, you might notice a decrease in performance accessing ODBC System Datasources (DSNs). This performance decrease can be up to ten percent. |
| 31442 | When you edit a |
| 31443 | 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. |
| 31444 | This step-by-step article demonstrates how to implement the |
| 31445 | When marshalling data in-process using ActiveX Data Objects (ADO) |
| 31446 | If a Visual C++ application or dynamic-link library (DLL) aggregates ActiveX Data Objects (ADO) |
| 31447 | When sharing a single instance of a disconnected ActiveX Data Objects (ADO) |
| 31448 | When using Performance Monitor to watch Open Database Connectivity (ODBC) connection pooling statistics, the ODBC Connection Pooling object and all of its counters occasionally disappear from the list of items available in the |
| 31449 | When you create a view with either the View Designer or with CREATE SQL VIEW and using a Sybase ODBC driver to connect to a Sybase server, the view performance can be slow when you are working with large tables. |
| 31450 | When an embedded null-termination character in a |
| 31451 | 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. |
| 31452 | An application or service with large numbers (more than 500) of concurrently open ActiveX Data Objects (ADO) recordsets that are opened and closed frequently may experience a virtual memory leak that leads to memory fragmentation and out-of |
| 31453 | 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 |
| 31454 | The |
| 31455 | This article describes two different ways to check which version of Microsoft Data Access Components (MDAC) is installed on a system: |
| 31456 | After installing or upgrading ODBC files, you receive one of the following error messages: |
| 31457 | 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: |
| 31458 | 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 |
| 31459 | 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 |
| 31460 | 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 |
| 31461 | 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: |
| 31462 | The following error message occurs when trying to connect to SQL Server using ActiveX Data Objects (ADO): |
| 31463 | If your software component uses Internet component download to deploy Microsoft Data Access Components (MDAC) inside .cab files, multiple errors often result. The most common problems are that the component never displays and the user's com |
| 31464 | 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. |
| 31465 | When you use ActiveX Data Objects (ADO) with the Microsoft OLEDB Provider for ODBC Driver (MSDASQL), and you try to update a table using a server-side cursor, ADO uses positioned update by default. In this case, the MSDASQL provider calls t |
| 31466 | 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 |
| 31467 | If you try to open a server-side ADO recordset with the "Set NoCount" statement, you would always get ForwardOnly recordset. |
| 31468 | 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: |