using VFP as middle tier to do all the lifting versus stored procs on RDBMS

2006-07-31 Thread Michael Babcock
The discussion last week made me wonder where people stood on using VFP as the middle tier that it's been called best for in the past. If you have a non-VFP object using VFP as the middle tier, you can only get back single values and not a cursor (unless you're going to create an XML document

RE: using VFP as middle tier to do all the lifting versus stored procs on RDBMS

2006-07-31 Thread stephen . russell
From: Michael Babcock [EMAIL PROTECTED] The discussion last week made me wonder where people stood on using VFP as the middle tier that it's been called best for in the past. If you have a non-VFP object using VFP as the middle tier, you can only get back single values and not a cursor

Re: using VFP as middle tier to do all the lifting versus stored procs on RDBMS

2006-07-31 Thread Andy Davies
Paul Hill said You could use a cursor internally and create methods to navigate (GoTop(), MoveNext(), EOF() etc). The object would probably need expose a property for each field in the results. I played with this some time ago... So did I - with the .net beta - it worked just fine. iirc I

Re: using VFP as middle tier to do all the lifting versus stored procs on RDBMS

2006-07-31 Thread Michael Babcock
Andy Davies wrote: Paul Hill said You could use a cursor internally and create methods to navigate (GoTop(), MoveNext(), EOF() etc). The object would probably need expose a property for each field in the results. I played with this some time ago... So did I - with the .net beta - it worked just