We're currently in the process of starting to replace all the cursors/tables/views in our app's data environment with VFP-native cursor adapters, so as to help in our redesign of the app to support multiple back ends. Subsequently, we'd like to try to avoid using VFP-data specific functions and try to be more SELECT/SQL-oriented in our approach.

Prior to CA - when a user deletes a record from a form, it gets marked as deleted and can be reused at a later time if a new record is added to the same table. When working with VFP-native CA, we're kind of stuck on how to deal with deleting a record, and its aftermath. We'd like to allow the user to be able to re-add the same key, if need be. We also have some tables that have 2 or 3 key fields in the record as well.

Any thoughts would be appreciated.

Laterness,
Jon