I suspect that's what he's getting at too, and I agree, this is a pretty cool idea.

In the case of Error 13 "Alias is not found" the name of the alias that is not found is returned in the 3rd element of the array created with AERROR(), so you could use this information to attempt to open the table and RETRY the line of code that needs the table.

But this strategy would get a little tricky if you are in the habit of opening the same table multiple times with different aliases (or just using any alias that is different from the table's file name). Also, I suspect that certain types of attempts at table access to a non-existent alias would not be quite so generous as to tell us in the 3rd element what alias it wants.

Also, to enable your forms to use tables and views from multiple databases (sometimes necessary), you would have to implement code to search all open databases for the occurence of the name in question. Upon finding the name, the code would have to know if the name was a table or view, so it could know to use the NODATA clause if necessary (and how is the code supposed to know if the view being opened is parameterized or not, without opening it first?)

I really like this idea, but there seems to be a ton of details to work out.

Arnon, are you going to help? :-)






>I don't know if this is what Arnon means, but it seems pretty straightforward that one of the errors that gets trapped is accessing a cursor that's not open. If it happens the error handler opens whatever is needed.
>
>Pretty sweet idea, IMO.
>
>>> - open views in the error events - that is views are only opened when needed
>>
>>Could you expand on this?