>5. How many of the 700 or so numbered VFP errors can you successfully recover from programmatically, and allow execution to continue?>
>
>Not sure, but I suspect all of them.
>
>I am sorry, but you are mistaken. The answer is less than a dozen. You can recover from things like "Printer not ready" and "Multilocks must be on..." but how are you going to recover from a syntax error, "operator/operand mismatch", or "not a table"
>
>6. Why does a form's BufferMode? property accept only values 0, 1, 2 when CURSORSETPROP() accepts values 1, 2, 3, 4, 5 for BUFFERING?
>
>Haven't got a clue.
>
>Form's BufferMode is actually a locking strategyand have nothing to do with buffering at all! In fact the form will determine the buffering strategy for its tables all by itself, based upon their usage. The locking strategies are:
>
>0 None (default)
>1 Pessimistic
>2 Optimistic
>CursorSetprop sets the specific combination of the Buffering and Locking strategy for a given table as follows:
>
>1 Pessimistic None The only option for FP2.x, default for VFP, tables
>2 Pessimistic Row Lock placed by KeyPress Event. Record pointer movement forces save
>3 Optimistic Row Lock placed by TableUpdate(). Record pointer movement forces save
>4 Pessimistic Table Lock placed by KeyPress Event. Save must be initiated explicitly
>5 Optimistic Table Lock placed by TableUpdate(). Save must be initiated explicitly

Thanks for the clarification Marcia.

Regards,