Hello We are trying to write in a NF2.50 database from Lotus Notes 5.0.5 with the C/ODBC driver 2.50. Everything seems to work okay, but we have a problem with rollback: it seems that the C/ODBC drver doesn’t supports transactional writings. The same process works with an Access database. Has someone succeeded doing transactional writings with a C/ODBC driver? Toni
You cannot run field validation or any of Navision’s function (codeunits etc.) when inserting or modifying records using C/ODBC, that means you can’t do postings to Navision using C/ODBC in REAL-TIME. Postings will have to be done in a batch basis, there are 2 ways to it. 1. Using dataport, which on a periodic basis will import data to Navision from a text file, outputted from Lotus Notes or 2. Use C/ODBC to insert records to a temporary Navision table, which on a periodic basis will run a codeunit to process records in the temporary table and flush it. Anyway, we are all learning right, so i could be wrong here… jordan
Hi Yes, I know I can’t fire triggers from C/ODBC. But I’d like to do rollbacks: if something goes wrong during the external writing —writing that is of course done in a temporary table—, the database should not be modified at all… Toni
hi, then i would suggest that you use a dataport to do your import of external data. as long as the lotus notes is able to export the data to a text file (without fail…) then the text file can be imported later to navision. as we know navision’s atomicity in handling data, if the dataport fails halfway, nothing will imported to the navision’s database (in this case it is a roll back). jordan
Toni, I’m guessing that each write you issue using C/ODBC is treated as a complete transactions. I don’t think there is a way to do multiple C/ODBC writes inside a transaction. If you need that functionality, and you want to do external writes, check out C/Front. 
Jim Hollcraft NCSD, NCSP, MCSE, CNE, MCP, MST aka Skater drilldot.com - Unauthorized Navision News
Hello After talking to Navision Spain, they confirmed that C/ODBC does a commit after each write… So there can’t rollback with C/ODBC. Thanks you all, Toni