Marc
I like ADO .. the Class and methods are standard whether you use Sql Server, Oracle, dB2 or Access.
Using ADO you can craft your recordset to cache your SQL results to the local client's memory ( which I think you mentioned in your post ) and once that fetch of records are on the client .. browses are fast and seamless .. data manipulation is very fast ..
There is more than one way to open and create a recordset .. FW has a set of functions that accomplish those tasks .. but I like to do it the ole fashioned way so I can assign my own parameters :
- Code: Select all Expand view
oRsLog := TOleAuto():New( "ADODB.Recordset" )
oRsLog:CursorType := 1 // opendkeyset
oRsLog:CursorLocation := 3 // local cache
oRsLog:LockType := 3 // lockoportunistic
Notice the CursorLocation parameter .. Ms Sql, Oracle, Access support these parameters ..
Rick Lipkin