I wanted to throw this idea out here for a sanity check: I would like to wrap data functionality (creating ADO connections, recordsets, etc) into a reusable class module, but I am wondering if this is redundant - putting another layer on top of ADO. I know the data environment already does this, but I don't really like to use bound controls and prefer to feed the controls with data and control data state myself. Any thoughts would be appreciated! Thanks in advance.

Paul