Kevin,

>1) Do I need to set the "DeleteCmd" property? Can't I just delete the record from
>the cursor and update the data?

You don't need to set DeleteCmd unless you want to override the normal default behavior of CA creating the DeleteCmd for you on the fly. You might need to specify it yourself if, for instance, you need to call a Stored Procedure for the delete.

>2) Can I use CA's to create an updatable cursor from more than 1 table, as in
>a JOIN or nested SELECT's?

Yes, but how well it works, I cannot say at this point. I have so far listened to the many voices saying "don't create a joined view that tries to update more than one table," and CA is really a "souped up" remote view. However, someone who has done it may say it's OK...