>For some reason you and Mike Helland are missing my point.

Or don't find value in it, thus disagreeing? Its not a crime.

This is what you said:

So, the create table command probably shouldn't accept quotes in the long name as it lends itself to confusion.

Keep in mind that this is the only thing I responded too ...

>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.

So? Why should the way VFP handle strings in commands be different for the NAME clause from every other place a string is used? Should:

create table 'Table1' name 'MyTable1' (cfield c(10))

throw an error? So you have to do:

create table 'Table1' name MyTable1 (cfield c(10))

Thats confusing. How about:

create table My Table name My Table (first c(10))
create table My Table name 'MyTable' (first c(10))
create table 'My Table' name My Table (first c(10))
create table 'My Table' name 'My Table' (first c(10))

Anyone familiar with the syntax and how to uses spaces in a string in VFP will tell you that only the last one will work (if there were no spaces, all would), but its less confusing if only the 3rd one (your syntax) would run?

>I made an long name and VFP changed it.

I agree, but that shouldn't change the syntax of a charcter string in one clause to be inconsitant with the rest of the product. If anything needs changing it should be that it doesn't replace spaces with underscores.