Another point I would like to make here [which was prompted in part by Jim Nelson's reply to me elsewhere in this thread] is that the major selling point of the CA is the ability to change the data source [e.g., upsize from VFP to a SQL DB or switch between DBs] very easily just by changing 1 or 2 properties in the CA. If you start designing your CA with commands that can only be interpretted by VFP, you have defeated one of the major purposes of the CA.

This is why the CA VCX Builder I created and have made publicly available is now a valuable tool for me. This builder will create a CA subclass for every table in a database whether it is a DBC, SQL Server or Oracle. I can then use any CA in that VCX in the DE of a form. If my data source changes, all I have to do is change 1 or 2 properties in ONE CA class in the VCX and I am done since all the table-specific CA subclasses in that VCX are subclasses of the main CA class in that VCX.

If you are interested in the builder and other CA example files, go to http://www.mctweedle.com and click the FoxPro Tools link.