>>> - open views in the error events - that is views are only opened when needed
>>
>>Could you expand on this?
>
>Basically Y'all got the idea
>Since we were using views and not tables directly we didn't have the alias problem
> - though this can be solved with a dedicated reference table - containing alias/real table names (If all system tables are stored in a seperate database you know where to find the reference table)
>Same mechanism can be used for multiple databases or as you said you should scan all the open databases
>
>One other thing is that you have to set a flag the first time you trap the error - so that if the table/view really does not exist you can trap the error and not go into an infinite loop
>

And how do you know to issue NODATA when opening the view? The parameter, even if defined in the offending routine, would not be in scope in the error method.