RE: Autonumber field alway set to 0 using OLEDB? Using ODBC work

Thank you for your help.
I was able to resolve the issue by testing for the field attribute
"adUknownUpdatable" in SQL and "adUpdatable" for ODBC and OLEDB. This
resulted in the correct determination of a field as an autonumber field.

Since we were getting the wrong value for adUknownUpdatable in OLEDB we were
overwritting the autonumber field wit null value which caused the problem.

--
Thanks
Morris


"Kevin Yu [MSFT]" wrote:

> Hi Morris,
>
> Thanks for providing me with the further information. Since you've already
> had the server side cursor, the KB article might not suitable for this
> situation.
>
> Could you let me know, which version of ADODB library you're referencing?
> If you're using an early version of ADO library, you can download MDAC 2.8
> sp1 from the following link and using the lastest version of ADO(2.8).
>
> http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-
> a9e0-3a1afbd5922e&DisplayLang=en
>
> Also, you can install the latest service pack of Jet 4.0. Please visit the
> following link and pick the version according to your OS.
>
> http://www.microsoft.com/downloads/results.aspx?freetext=jet+4.0+sp8&product
> ID=&DisplayLang=en
>
> If that still doesn't work, could you please build a small sample that can
> reproduce the problem? You can send it to me by email directly, so that I
> can deliver my assistance more quickly. Remove 'online' from the no spam
> alias is my real email. Thanks for your cooperation!
>
> Kevin Yu
> =======
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
>
>
.