> Why not wrap an if() around that first line and then execute the commit, > else insert until positive or 20 attempts have been made >
Back in the days I had been using Oracle 8.2 (late 1990s) I used to have to do exactly that. I could not rely on Table Level Buffering to work on an updateable view on an Oracle table(s). I had to use Record Level Buffering, and verify each and every update to ensure the write was committed. I suspect the problem was in the ODBC, as M$ was not feeling too wild about writing a solid Oracle ADBC, and the Oracle ODBC just was not up to the task with VFP v-3 or v-5. Once I parted ways with the company that tried to move from a VFP back end to Oracle (and M$ SQL Server, which was really horrid to work with back then) I went back to a pure VFP back end and all my update problems went away. I have not yet run into any problems writing to PostgreSQL via ODBC with VFP - but if I do I would use the same technique Stephen suggested. Gil > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Stephen Russell > Sent: Monday, April 14, 2008 9:27 AM > To: [EMAIL PROTECTED] > Subject: Re: SQL Pass Thru question > > > On Mon, Apr 14, 2008 at 5:22 AM, Graham Brown (CompSYS) > <[EMAIL PROTECTED]> > wrote: > > > Hi > > > > I've written a simple routine to upload into Quickbooks via the > QODBC.com > > link. What I'm finding is periodically some records are not getting > > written > > into quickbooks. I can run the insert statements manually and > they work so > > I > > suspect it has something to do with firing the inserts one after the > > other. > > > > Does SQLExec need a delay loop to wait until it has finished executing > > each > > insert command? > > > > This is the code for QB. It looks to see if the customer record > is already > > on file, inserts if not then checks again to see if went > through, finally > > it > > adds a child record for the job card. > > > --------------------------------------------------------- > Are you taking for granted that QB is accepting your insert? > > =SQLEXEC(nH,cSQL) > =Sqlcommit(nH) > > Endif > N=N+1 > > Why not wrap an if() around that first line and then execute the commit, > else insert until positive or 20 attempts have been made > > > -- > Stephen Russell > Sr. Production Systems Programmer > Mimeo.com > Memphis TN > > 901.246-0159 > > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
