I have some questions regarding the RecordSet class that I hope somebody can help me with.
1) You execute a query and have a RecordSet. Does the RecordSet maintain the entire current record in memory, the entire collection of records, or does it only read data from the database on demand, i.e. when you call RecordSet.Field? (I'm *guessing* it holds the current record in memory, which is why you can't move backwards with some databases.) 2) Is there any penalty for keeping an open RecordSet around for a long time? What if there are a lot of open RecordSets? Here's why I'm asking. I have a project with a lot of tables. For this project, in some ways it would be beneficial to wrap records in classes, but I'm not sure if it would be best to query, read RecordSet data into properties, then close the RecordSet, re-opening it later and mapping property-to-field for updates. OR if it would be better to keep the RecordSet in a private property of the class, and have public properties which actually just read from/write to the RecordSet in real time. I'm tempted to do the last one in this case. Any thoughts on this? Daniel L. Taylor Taylor Design Computer Consulting & Software Development [EMAIL PROTECTED] www.taylor-design.com _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
