Did you try adding the TABLEUPDATE() statement before your SQLCOMMIT()? My point was getting you to look at using SPT to make the data changes directly to your data without retrieving a cursor, making the cursor updatable, changing the data, etc. The direction you take is up to you. If you want to continue making the cursor updatable, you will need a TABLEUPDATE() statement before the SQLCOMMIT.

When I looked at your code, it looked like you were retrieving data from the server based on some value in the table or cursor you were SCANning through. I just took that value and used it as the criteria for determining which record in the server table to update with your new data values. That is all a remote view does anyway when you call the TABLEUPDATE function.

>I don't see how this will work. Where is the particular record to update defined? webprddt6 is an as400 library. The drawmstrp is the table and dm_drawing_number is the key field of the record. I have a minimum of 950 records I need to loop through and change field data. One of my major problems is an inconsistency with how dm_drawing_number is named. In my associated table(the one I am scanning from) I have engineering part numbers: example 841523-401, 856235-1, 845787-201. I need to look into the as400 database and find the respective engineering drawing number for these parts. In some cases my engineering drawing number is a six charactor number with embedded sub numbers(our old way) Now we are creating mono drawings(one drawing for one part) That makes to drawing number ten charactors. As I loop through I need to check first for the ten charactor style, if not found the the six charactor style, when found change the data in a couple of fields.
>
>I hope this makes sense.