I changed the connection to work off Native and that appeared to work.

I then tried it with DB2 (ODBC) and I get a new error.

I am able to connect and insert a record. When I issue a Tableupdate() it returns false but a record is added to the DB2 table. The cursor does update the KeyID field but it always updates to the value 1.

The error I get is: "The refresh key defined for table CCMD is not unique."
I have no idea where it got the table "CCMD", I can not find it in code anywhere.


>I am guessing here, but I think the auto refresh feature bundles 2 SQL command via the provider. That's why the multiple step error. Again this is still just guessing, but the VFP provider may not support this. I will check it out and see if I can get it to work against the Northwind DBC. I know it works with Oracle and you can bet the farm it works with SQL Server.
>
>>I changed the Connection String to the VFP OLEDB added the table but I get an error on the Tableupdate. 1435 - "Microsoft Cursor Engine : Multiple-step operation generated errors. Check each status value."
>>
>>I used "Provider=VFPOLEDB.1;Data Source=C:\tmp\A.DBC;Mode=ReadWrite|Share Deny None;Password="";Collating Sequence=MACHINE"
>>
>>
>>>The code below is ORACLE demo code I use to test these features. BTW, they work like a dream! Create you a presidents table with the structure like what I have in the CA below. Make the KeyID field an Identity field. You will also need to tweak the ADO connection string.