How to create and resolve "ODBC- update on a linked table Libraryname_ Filename' failed. [IBM][System i Access ODBC Driver][DB2 for i5/OS]SQL7008- Fil (1 Viewer)

c32

New member
Local time
Tomorrow, 04:20
Joined
Mar 27, 2022
Messages
4
Hi,

How to create and resolve below error while trying to update any file (which is there on IBM i(AS/400) ) USING MS Access:-

"
"ODBC- update on a linked table Libraryname_ Filename' failed.
[IBM][System i Access ODBC Driver][DB2 for i5/OS]SQL7008- Filename in
libraryname not valid operation.(#-7008) "

For the file which is not journaled and even journaled, I tried all the
below Commit mode options in Advance server options still could not
generate this error :-

Commit mode:

Commit immediate(*None)
Read uncommited (*CHG)
Read commited(*CS)
Repeatable read (*ALL)
Serializable (*RR)

***************************
also tried by changing various Connection types available under IBM i
Access Windows ODBC Driver Connect:

1) Use ODBC access mode
2) Use ODBC access mode, Call allowed
3) Limit to Read/Call(Select and Call statements allowed)
4) Limit to Read-Only (Select statements only)

But could not generate that error(SQL7008) so someone could please help to understand how to create this error and then resolve this error with proper steps and examples.


Thanks.
 
Welcome to the forums! We are the most active Microsoft Access community on the internet by far, with posts going back over 20 years!

To get started, I highly recommend you read the post below. It contains important information for all new users to this forum.

https://www.access-programmers.co.uk/forums/threads/new-member-read-me-first.223250/

We look forward to having you around here, learning stuff and having fun!
 
Welcome @c32 to the best online forum for Ms Access Developers.
 
yes, i tried almost every thing but unable to create this error ?


Thanks
 
Well you can just raise the error, if you want to test what your code does, when that error ever happens.
 
i tried updating file using ms access and tested it for both the scenarios 1) when file was journaled 2) not journaled.

for both the case i was unable to create this error so not sure how could i create it then resolve this error?


Thanks
 

Users who are viewing this thread

Back
Top Bottom