BUG: Error 3622 Open SQL Server Table with Identity ColumnID: Q190620
|
When you try to open a Dynaset in Visual Data Manager (or Visual Basic
sample project VisData) against a SQL Server 6.5 table that contains an
Identity column, you get the following error occur:
Error 3622 - You must use the dbSeeChanges option with OpenRecordset when accessing a SQL Server table that has an IDENTITY column.
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.
You can modify the VisData sample to avoid the error. There are two places
that you need to make the changes. The first is for opening a recordset
from the Database Window; the second is for when executing a SQL statement.
Set rsTmp=gdbCurrentDB.OpenRecordset(rName, dbOpenDynaset)
-to-
Set rsTmp=gdbCurrentDB.OpenRecordset(rName,dbOpenDynaset, dbSeeChanges)
Set rsTmp = qdfTmp.OpenRecordset(dbOpenDynaset)
-to-
Set rsTmp = qdfTmp.OpenRecordset(dbOpenDynaset, dbSeeChanges)
Create Table IColTest
(Id_Col int Identity, Name VarChar(30) Null)
Create Unique Index IIndex on IColTest(Id_Col)
Additional query words: kbDSupport kbdse kbvbp600bug kbAddIn kbDatabase kbdse
Keywords :
Version :
Platform : WINDOWS
Issue type : kbbug
Last Reviewed: June 22, 1999