Search results for query: *

No problem. Sorry for taking the thread off topic.

Mike, Opera bespoke is my specialist area... I was involved in the Pre Opera Sequel programme and have been developing with the product since then. If I can be of help let me know. Tim

Thanks Guys, I'll probably look into the DLL option. The CSV one would work but it ins't really the seamless idea I had in mind. If it's of any future use I have recently written an Opera to Sage conversion program which uses the csv method of Sage import. Tim

Thanks both of you, after further rummaging I think I may have the answer here... http://www.accessmonster.com/Uwe/Forum.aspx/access-externaldata/1473/ODBC-SAGE-LINK Looks like it may well be to do with a read only ODBC being shipped with the standard product or something similar. Mike: Thanks...

Mike, Well yes odd though it may sound, I figured that if the wizards didn't work then at least I could code it and try to work out what was going wrong, which at least has enlightened me about ODBC a bit but hasn;t worked any better. The ODBC driver I am using is the Sage Line 50 v11 one...

Thanks for that Mike, Sadly I tried all of that to begin with which is why I went down the route of doing it the hard way. It seems to be getting hung up on the Key Index fields for some reason. Could it be something to do with the ODBC drivers ?

Hi, I'm trying to update via ODBC using a cursor as per http://www.tek-tips.com/viewthread.cfm?qid=812206 but when the curor moves off the current record to update I get Connectivity Error Invalid Keyword Specefication. The current code I am using looks like... CLOSE ALL CLEAR ALL CLEAR...