You should always get an error as SELECT 0 will select the first unused work area, meaning there will never be a table open there, so ALIAS() will return an empty string.

No error occurs.

My message is a simple example for repro the behaviour.

My problem is clear:
if my application go into a bad path, and the current workarea is empty,
commands like:

SELECT .... FROM currentworkare
go top
seek expression
filter ...
bla bla bla .... bla

non fire a error, but open a dialog.
With alias fixed, the problem is introduced however:

SELECT * from ambarabaciccicocco

i get this:
- open a dialog
- if i push cancel, then it fire a error.
I do not want that VFP open the dialog

Thanks

Fabio