Hi all,

New to the forum. I'm in charge of migrating a very complex enterprise legacy VB6 app to run under a 64bit version of Windows 7. Getting the VB6 IDE running on Win7 was fun enough, but this issue is just driving me nuts.

The lowdown: the app uses an ADODB provider to insert the contents of a Recordset to a Sybase DB table. The VB project references Microsoft ActiveX Data Objects 2.8 Library on XP, I know Windows 7 uses the newer 6.0 version of this library. I've spent hours reading up on MSDN and various forums on possible breaks that this later version of MSDASQL could create for an app written on XP and running on Win7 but haven't found anything like the issue I'm experiencing. I can connect through this provider no problem, but the error occurs when trying to execute the "Update" method on the Recordset object. I get a Foreign Key Constraint Violation (Sybase error 546). My best guess is that somehow this new ADODB provider is screwing up the order of my data and trying to input the wrong data in the wrong columns thus throwing me the FK constraint violation error.

Any idea what I can do? I have a lot more details I can provide, but don't want to write a whole essay for the time being.

Thanks in advance for any help!