>Thanks for the clarification Marcia.
>
>No sweat < s >. Actually, I am very familiar with those questions. They were a set put together by Andy. PAul Maskens and myself back in 1999/2000 when Andy and I were working with PAul. We were using them to help us spearate the wheat from the chaff when we were interviewing prospective employees.

Hi Marcia,

Well, heck. It's not fair if you wrote the questions. :-)

To me, both questions are somewhat ambiguously phrased.

For example, assuming something like "syntax error" or "not a table" occurs in an isolated procedure called, say, from a menu item, then in many if not most cases I certainly can "recover successfully programmatically" by issuing a warning to the user and then calling RETURN TO Mainloop in my error handler, and as long as the user heeds the warning and doesn't call the faulty procedure again, execution of the rest of the program can continue--at least long enough to achieve a graceful exit without loss of data. Given this mindset, my answer would have been "all but the untrappable ones, like those in reports, out-of-memory, nesting level exceeded, and C5s".

The BufferMode question can be read to mean, "How come the VFP designers did BufferMode the way they did in forms, when you really need to pay attention to both locking and buffering strategy?" Your response here indicates that you were looking for something else: "What's the difference between Form.BufferMode and CURSORSET/CURSORGETPROP("Buffering")?" But I've scratched my head more than once on that one, wondering what it was the questioner really wanted to know.

So, tell us, what's the scoop behind the rest of the questions? <g>