The idea is the VFP transactions do not help in a SQL Server environment; they're meant only for local/network DBFs. A client server VFP application usually does not contain BEGIN TRANSACTION/ROLLBACK/END TRANSACTION; instead, the corresponding SQL Server commands are issued over the connection.
> -----Original Message----- > From: [email protected] [mailto:profoxtech- > [email protected]] On Behalf Of Rafael Copquin > Sent: Thursday, July 29, 2010 11:46 PM > To: [email protected] > Subject: Re: VFP,SQL Server and transactions (SQL Server Express 2008) > > Can you show me an example of a SP for the header table and one for the > details table? > > Also, from your reply I understand that you advise me not to use VFP > transaction code at all > > What about CA's? > Should I replace them for regular cursors to be saved via the SP? > > I developed all my code after reading the book > > Client-Server Applications with Visual FoxPro 6.0 and SQL Server 7.0 by Chuck > Urwiler and others > > but when they wrote the book, CA's did not exist, they were talking about > views. But then I know that a cursor adapter is a wrapper for a view > > So what gives? I am very confused with this > > Rafael > > > El 29/07/2010 17:15, Stephen Russell escribió: > > If I were you I would generate stored procedures for your CRUD code > > and have VFP call them. > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] 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.
