Mike,

The reason your examples throw errors is because there is inconsistency between the actual filename and the NAME (I didn't even know the NAME clause existed before you posted this thread) stored in the DBC. Frankly, I see very little value in ever trying to do that It only leads to huge maintenance headaches IMHO.

>Hi Dave.
>
>For some reason you and Mike Helland are missing my point. I thought my examples were clear enough. I only referred to the file name as Junk and the rest of the examples worked with the long name.
>
>The name portion of the create table command (not the disk file name) is where the inconsistency lies.
>
>I'm only talking about the NAME clause.
>
>The NAME clause is supporting quotes and then converting the quoted value into a non quoted value. The non-quoted value is then the only applicable value in other commands. Therefore, its confusing for the NAME clause to accept the quotes when the other commands won't.
>
>create table "junk.dbf" NAME "this is a long name" (field1 c(10))
>use "this is a long name" && The use command doesn't work.
>
>use This_Is_A_Long_Name && this works.
>
>remove table "this is a long name" && doesn't work
>remove table "this_is_a_long_name" && works.
>
>That's goofy. I made an long name and VFP changed it. So now, I have to know what the long name will be. So the NAME clause should not support the quotes. I would be forced to write the code using the alias that VFP obviously intends I use.