In a general sense, there has been significant debate about whether or not one should ask ADO to construct Recordsets that can be updated through the ADO mechanism more or less directly. That is, should you create a cursor that knows how to make changes to the underlying data? As we progress through this chapter, there will be more discussion about this subject, but the bottom line tends to favor creating and using read-only Recordsets and managing the update operations yourself in code. Even if you only compare the sheer volume of data passed when requesting a RO vs. a read-write (RW) Recordset, you'll see why this recommendation is made so often. Use the Recordset.Save method to save each Recordset to a file and compare the sizes.