ODBC update error with DB2 timestamp data

[kaming]

Dear all,

I found that I can't update or delete a DB2 record with timestamp using
Access through ODBC. The Access complains "No current record" while I
attempt to update or delete the record with timestamp.

Do anyone have idea of how to fix this problem?

Thanks in advance!

Henry

[Mark A]

"kaming" <gu***@guest.com> wrote in message
news:cs*********@imsp212.netvigator.com...

Dear all,

I found that I can't update or delete a DB2 record with timestamp using
Access through ODBC. The Access complains "No current record" while I
attempt to update or delete the record with timestamp.

Do anyone have idea of how to fix this problem?

Thanks in advance!

Henry

Try downloading the DB2 client (free) and use the IBM supplied driver. You
want the Runtime client for 32 bit Windows.
http://www-306.ibm.com/software/data...v8.html#WIN-32

[kaming]

Thanks Mark!

In fact, I have already downloaded the latest client and using the IBM ODBC
driver 8.01.08. However, it still not work ..
I have tried a work around by using two fields for time and date and it
works (Access can update or delete a record).
Or is there any trick to do with the ODBC driver??

Thanks!

Henry

"Mark A" <no****@nowhere.com> wrote in message
news:fM********************@comcast.com...

Try downloading the DB2 client (free) and use the IBM supplied driver. You
want the Runtime client for 32 bit Windows.

http://www-306.ibm.com/software/data...v8.html#WIN-32

[Mark A]

> Thanks Mark!

In fact, I have already downloaded the latest client and using the IBM ODBC driver 8.01.08. However, it still not work ..
I have tried a work around by using two fields for time and date and it
works (Access can update or delete a record).
Or is there any trick to do with the ODBC driver??

Thanks!

Henry

I really don't know. I think it is just an incompatibility between Access
and DB2. MS provides this interface, but Mr. Gates not very happy that you
are using it against a non-MS database, and they often play lip service to
support issues for non-MS products.

[wfs]

On the driver I have, there's an option ("Advanced CLI/ODBC Settings -
Service - Patch1 - Describe Timestamps as CHAR(26)' - that may do what you
want.

Bill

"kaming" <gu***@guest.com> wrote in message
news:cs*********@imsp212.netvigator.com...

Thanks Mark!

In fact, I have already downloaded the latest client and using the IBM
ODBC
driver 8.01.08. However, it still not work ..
I have tried a work around by using two fields for time and date and it
works (Access can update or delete a record).
Or is there any trick to do with the ODBC driver??

Thanks!

Henry

"Mark A" <no****@nowhere.com> wrote in message
news:fM********************@comcast.com...

Try downloading the DB2 client (free) and use the IBM supplied driver.
You
want the Runtime client for 32 bit Windows.

http://www-306.ibm.com/software/data...v8.html#WIN-32

[James]

wfs points out:

On the driver I have, there's an option ("Advanced CLI/ODBC Settings -
Service - Patch1 - Describe Timestamps as CHAR(26)' - that may do what you

This should allow you to delete. Since there is no TIMESTAMP in MS Access,
you will need to format a character string as a timestamp to update
directly.

[Klemens]

I got the same problem with bigint but I can't find a patch for this.

Klemens

"James" <Ja***@someadd.net> schrieb im Newsbeitrag
news:2o********************@comcast.com...

wfs points out:

On the driver I have, there's an option ("Advanced CLI/ODBC Settings -
Service - Patch1 - Describe Timestamps as CHAR(26)' - that may do what

you
This should allow you to delete. Since there is no TIMESTAMP in MS Access, you will need to format a character string as a timestamp to update
directly.

[Bob Hairgrove]

On Sat, 22 Jan 2005 11:00:15 +0800, "kaming" <gu***@guest.com> wrote:

Dear all,

I found that I can't update or delete a DB2 record with timestamp using
Access through ODBC. The Access complains "No current record" while I
attempt to update or delete the record with timestamp.

Do anyone have idea of how to fix this problem?

Thanks in advance!

Henry

I'm really surprised that no one up to now was able to tell you why
this will never work ... DB2 supports fractions of a second to six
decimal places (i.e. microseconds) and Access only goes to a
granularity of one second (no fractions). No patch exists because this
is an impossible thing to do. Access will never be able to distinguish
rows where the difference in timestamp values is less than one second.

The Access DATETIME data type is mapped to the ODBC data type
SQL_TIMESTAMP, but ... no fractions.

Note that MS-SQLServer uses yet another kind of "timestamp" data type
(a kind of AutoNumber automatically generated surrogate key) which has
nothing to do with the ODBC SQL_TIMESTAMP type.

Good luck.

--
Bob Hairgrove
No**********@Home.com