Please see my other reply first! As I said there, I don't consider this a bug. But because I know you like to find bugs in VFP, here's one related to the aliases assigned by default :). (You know, there must be one! :))

Create two new tables: one called "w1000.dbf", the other called "1234.dbf". After that:

CLOSE DATABASES
SELECT 1
USE W1000
?ALIAS()
SELECT 1000
USE 1234
?ALIAS()

Bingo! Both tables have the same alias (W1000)! Is this a bug? :)

Vlad

>Vlad,
>
>So how would you define this, if not as a "bug". . .
>
>As you know, FP/VFP will use the table name as the alias when no alias is specified.
>
>With a table named "3CHR" one does *not* get the alias of 3CHR, ostensibly because, as you said, an alias *must* start with a alpha character or a underscore.
>So we have an "incomaptability" between USE and ALIAS in some cases. Is this a "bug"????
>
>Cheers,
>Jim N
>
>>>>Have you tried renaming the libraries like this:
>>>>
>>>>VCX_1500.vcx and VCX_2360.vcx
>>>>
>>>>and then accessing them?
>>>>
>>>>This reminds me of using sys(3) to generate a unique name which
>>>>turns out to be a numberic name. When foxpro uses it, it gives
>>>>it an alias like A OR C, etc.
>>>
>>>Carl,
>>>
>>>What we did was issue a
>>>SET CLASSLIB TO 2360 ALIAS C2360
>>>
>>>That works.
>>>
>>>However, anothere interesting tidbit is the fact that you cannot issue
>>>SET CLASSLIB TO 2360C
>>>
>>>You get a syntax error.
>>>
>>>Wayne
>>
>>As far as I know, this is an old problem in FoxPro. But this is not a bug, since an ALIAS must start with a letter or underscore.
>>
>>Vlad