Two points you have to consider, both of which are related, are:
1) 123 is not a valid alias - an alias starts with a letter or underscore. VFP will replace the alias with something that does start with a letter. Type the SET command to see what aliases are open.
An alias is the name VFP uses internally for the table. It is usually the same as the table - but not if the table doesn't conform to certain naming rules.
2) SELECT 123 will select work area # 123, not an alias with name 123, which can't exist in VFP. Area #123 is probably empty; if you open 10 tables, they will usually be open in areas #1-10, for example.
To avoid problems, you might start all table names with letters, for example, T123.dbf.
You can also specify an alias explicitly when opening a table. The following example shows one case where this might come in useful, apart from tables with invalid names (invalid names includes names that contain hyphens):
use January alias MonthlyData
...
select MonthlyData
scan
...
>Dear Experts
>
>When I run following line of codes, then it works fine
>
>CLOSE ALL
>CREATE TABLE abc (sno n(3))
>insert into abc values(10)
>
>select abc
>brow
>
>But When I run following codes, then it generates this error message
>No tables is open in the current work area
>
>CLOSE ALL
>CREATE TABLE 123 (sno n(3))
>insert into 123 values(10)
>
>select 123
>brow
>
>What done when I replace table name 123 instead of abc?
>Please help
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)