I was sure that was what you meant. :-) I just wanted to point out to Elyse that even if your suggestion got around her immediate SDT problems, she would still need to go back and make the proper changes to avoid future problems.

>Absolutely, Al. You notice I said "Temporary" fix. Reserved words can cause problems in strange places - the one I see in every project I've ever worked on is a field named DESC for "description". Works just fine until it's in the wrong position of an SQL query.
>
>
>>Hmmm... are you certain that all VFP commands that can reference an alias will work properly with an alias of "FIELDS"? If not, it would be better to accept that a mistake was made and do all the fixes now. This is the sort of situation that can come back to haunt you if not fixed properly.
>>
>>>As a temporary fix, you might consider renaming the table to "MyFields" (or whatever) and then adding an ALIAS FIELDS clause wherever you have used it. This way the only code that will have to be changed will be the lines where you open the table.
>>>
>>>HTH
>>>Barbara
>>>
>>>>One of my databases contains a table named "fields." I get an error whenever I try to modify this table in Stonefield. I suspect it is because of the table name causing a conflict. Is this true?
>>>>
>>>>Elyse