"No current record" error updating linked DB2 table from Access

[RCPD700]

Rows were appended to a DB2 table by a batch COBOL application and the commit was successful. All rows in the table can subsequently be viewed using Access. Any attempt to update or delete any of those rows gets error message "No current record" despite the row(s) being selected.

If you add rows using Access, you can update/delete them using Access without problem. If you select multiple rows for deletion, only those rows existing before the insert/append or those added with Access get deleted. Message is issued for all others (with the option of suppressing repetitive messages after the first).

Our DBA believes ODBC is not the problem because using the DB2 Command Center on the desktop you can select rows for viewing and update/delete any row you like. WinSQL also works fine... Access 97 and Access 2000 both return that same message.

Are there any security issues that could be causing this? Any other things we could/should check... ideas?

 

[RCPD700]

After further investigation we determined that the timestamp column was causing the problem. I inserted several variations of timestamp data with the same OS/390 batch application and discovered in the process, that the problem is with the milliseconds portion of the timestamp. DB2 allows 6 positions in the milliseconds portion, but Access (both 97 and 2000) can only handle the first 3 positions.

Using today's date and current time as an example:
2001-07-29-18:46:38.999000 would be handled fine by Access
2001-07-29-18:46:38.000100 would cause the problem as would any other
significant digits to the right.

Hopefully this is clear enough. If anyone needs additional information, or clarification, feel free to contact me via e-mail at jrwilson@co.sanmateo.ca.us