I understand....OK, how about code in Cursor.Error event? Should encapsulate the error into the specific cursor?


>Well, that sort of gets away from the visual DE...
>and i can't afford to open all my tables twice... I have a couple of forms with 15-20 cursors in the DE. Thanks though.
>
>
>>Hi Erik ---
>>
>>You want a kludgy way? In the BeforeOpenTables event of the DE, manually open each file one by one with a small custom ON ERROR to trap which one blows, if any. Then, at the end of the method...close the tables....the DE will reopen them right after that method ends anyway.
>>
>>
>>>I would lke to build into my framework (error handler, I guess) a mechanism that givesa a meaningful error message when a form tries to open and cannot open a table in its dataenvironment. Currently, my error handler throws up the generic 'file Access is denied', but doesn't tell you which file.
>>>I would like to give a message that says something like
>>>
>>>"This form cannot gain access to 'mytable'. Try again later."
>>>
>>>I know this could be handled fairly easily with a programmatic dataenvironment, I just wanted to know if anyone had any ideas on how to do this without abandoning the visual DE.