>The last thing you explained is what I thought of, I mean, the separate cursor and so on. That would led me to ask if there are events in CursorAdapters, not views, that could do that job done, just before saving my changes.
>
>On the other hand I don't have a guide that let me develop using CursorAdapters instead of remote views. If anyone could help me with this last topic, that would be a big, big help.

When I first tried out the CA, I ran into trouble, because I tried the builder supplied with VFP or some book examples, and it didn't work. Then I got it as part of someone else's framework code and lived happily ever until retirement... Sorry, not disclosable, not my code.

The general rule of thumb is that you should code your own CA base class, and do it in a .prg file. Then instantiate that, again in code, wherever you may need it, optionally subclassing for special cases, i.e. when you want to add code for some events not covered by your base class. Saves a lot of work, time and hair. Also, do not attach an adapter to a table, let it create the cursor by itself. Almost all things that you used to do with cursorSetProp() are now properties of your CA object... except, IIRC, buffering (or was it locking?), which seems to work only when the cursor is created, but can't change it on an already opened cursor. That's where you have to call CursorSetProp