Hi Mark,

I agree with you that the major selling point for CA is allowing to change data source. I have the following questions:

1. When will the DeleteCmd property be used? Based on my scenario #2, it will be used when I clicked the delete column of the grid. However, it is not used in my scenario # 5 where the delete statement is executed by clicking a button outside the grid.

I cannot find any sample which shows how to update, insert, delete on a form with CA. All the samples that I found only show how to display data using different data source. I believe another major selling point for CA is the ability for us to control the update, insert, delete actions.

2. Why do BeforeDelete and AfterDelete events not fired if I added tableupdate() in the delete event of the grid and clicked the delete column of the grid.

I have downloaded your CA VCX builder. I believe your tool is very helpful in building a new application. I remember that you have mentioned in this website that Doug Henning has a wizard which will convert cursors in the DE of existing forms to CAs. How can I find more information about that wizard?
I'm interested in knowing what other area such as requery() need to be changed after such wizard. I wonder how much work to convert an existing application which uses foxpro tables w/o local views to CAs and an existing application which used remote views to update SQL Server tables through ODBC to CAs.

Thank you,

Peter