RE: Autonumber field alway set to 0 using OLEDB? Using ODBC works fi
- From: v-kevy@xxxxxxxxxxxxxxxxxxxx (Kevin Yu [MSFT])
- Date: Sat, 28 May 2005 08:34:48 GMT
Hi Morris,
First of all, I would like to confirm my understanding of your issue. From
your description, I understand that when you're using Jet 4.0 for oledb
provider to insert records to an Access 2000 database, the auto number
field value is always 0. If there is any misunderstanding, please feel free
to let me know.
Based on my research, this is a known issue. I assume that you're using a
client side cursor. You can try to check the following KB articles for more
information and resolutions on this issue.
http://support.microsoft.com/?id=190370
http://support.microsoft.com/?id=195910
http://support.microsoft.com/?id=221931
HTH.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
.
- Follow-Ups:
- RE: Autonumber field alway set to 0 using OLEDB? Using ODBC work
- From: Morris Neuman
- RE: Autonumber field alway set to 0 using OLEDB? Using ODBC work
- From: Morris Neuman
- RE: Autonumber field alway set to 0 using OLEDB? Using ODBC work
- From: Morris Neuman
- RE: Autonumber field alway set to 0 using OLEDB? Using ODBC work
- From: Morris Neuman
- RE: Autonumber field alway set to 0 using OLEDB? Using ODBC work
- References:
- Autonumber field alway set to 0 using OLEDB? Using ODBC works fi
- From: Morris Neuman
- Autonumber field alway set to 0 using OLEDB? Using ODBC works fi
- Prev by Date: ANN: Updated lists of OLE DB providers, .NET providers, ODBC drivers, etc.
- Next by Date: RE: Autonumber field alway set to 0 using OLEDB? Using ODBC work
- Previous by thread: Autonumber field alway set to 0 using OLEDB? Using ODBC works fi
- Next by thread: RE: Autonumber field alway set to 0 using OLEDB? Using ODBC work
- Index(es):
Relevant Pages
|
|