![]() ![]() RDO control RowsetSize or KeysetSize was set to incorrect value. The Property value is out of range or incorrect.ĪctiveReport, CheckBox, Canvas, Field, TOC, Label, OleObject, Printer, RDOControl, Shape, Section, Barcode The Control or Section name already exists Only alphanumeric characters are allowed.ĭuplicate Name. NOTE: Read the Migrate_qfe.txt file that is included in the Migration.exe file included with the download.įor information about this hotfix as it applies to MDAC 2.GridX/Y out of range. If you are installing this fix onto a computer running Windows 95 or a computer with the original release of Windows 98, you might need to install the Windows 98 Migration DLL included with this fix. Important Notice for Microsoft Windows 95/98 Users Locate and rename the current version of Msdaprst.dll, which should be in the \Program Files\Common files\System\msadc folder.Ĭopy the hotfix version of Msdaprst.dll into the same location and restart your services and applications. This may include Internet Information Server (IIS), Microsoft Transaction Server (MTS), Microsoft Distributed Transaction Coordinator (DTC), and any ADO or OLE DB applications.ĭownload the hotfix version of Msdaprst.dll into a temporary folder. Please see the REFERENCES section of this article for more information.Ĭlose or stop any applications or services that are using Msdaprst.dll. While it is not expected that any fatal errors occur if this hotfix is applied to MDAC 2.1 SP2, doing so is strongly discouraged.Ī separate hotfix exists to address this problem in MDAC 2.1 SP2. In order to alleviate memory fragmentation problems, significant code changes were made between MDAC 2.1 SP1 and MDAC 2.1 SP2. This hotfix should only be used with machines running MDAC 2.1 SP1 (version ) or earlier. It is not recommended that you install this hotfix on a machine that is currently running MDAC 2.1 SP2 (version ) or later. Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.įor the latest version of Microsoft Data Access Components (MDAC), see the following Microsoft Web site: The English version of this fix should have the following file attributes or later: The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question. EN-US CNTACTMSNOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Data Access service pack that contains this hotfix. Apply it only to computers that are experiencing this specific problem. When subsequently constructing the UPDATE statement, this metadata is not available and incorrect syntax is generated.Įxamination of trace logs show that the correct syntax was used when selecting the records, but only the table name was used when constructing the UPDATE statement.īecause the Connection currently points to the database containing the stored procedure and the table does not exist in that database, "Invalid Object Name" errors are returned.Ī supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. The remoting portion of ADO (Msdaprst.dll) is inadvertently overwriting portions of the metadata contained in the recordset. If the recordset is never marshaled out of process but is delivered directly to the process that is attempting to update it instead, the UPDATE statement succeeds. ![]() That recordset is then passed out-of-process as a disconnected ADO (ActiveX Data Objects) recordset to another client application.Īn attempt is made to update the disconnected recordset. The resulting recordset is returned to an application or service. This error message occurs under the following conditions:Ī SQL Server stored procedure exists in one database that selects records from a table in a different database. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |