Q: I have been going through the recordset tutorials. They are great at demystifying recordsets. You did not mention recordsetclone. I assume if the table is bound to a form that's the way to go. That's why you used an unbound form. Regards Alan.

A: Alan, a RecordsetClone is basically a READ-ONLY copy (clone) of the data underlying a form. Clones are great for doing things like filtering forms, searching for records, and things of that nature. I will spend some time in a future class covering them. They have their uses... but they're nowhere near as powerful as stand-alone Recordsets. I wanted to show you how you can programmatically change and work with data without any kind of form or query object. That's why I used a lot of unbound tables. Recordsets are great for manipulating data that's not necessarily in the current form. The RecordsetClone property is good for performing non-edit actions on the current form or subform. I'll explain it better in an upcoming class.