Interesting ideas. Unfortunately I'm connecting to Btrieve data, rather than SQL. I'm a little unfamiliar with SQL server, but by what I hear form you, are you saying you can make views of your SQL data within SQL server? If so, that is pretty handy.

Thank you for the input. For the time being, I'm using (Gag) Dbftrieve to extract the problem field.

- Chris Holtz

>Your best bet is to create a remote view of the table that does not have the # character in the name and do your updates through this view. If you are using SQL Server this remote view would be a SQL Server view.
>
>I usually create views of all my SQL Server tables and then connect to the view through VFP remote views rather than the table.
>
>
>>I am connecting remotely to a table that has the field "Next_Trans#"
>>
>>Whenever I try to update the field, VFP comes back with Field Not Found Next_Trans
>>
>>It seems that VFP is having a problem with the # in the field name. Has anyone ever dealt with this kind of behavior?
>>
>>Thank you,
>>Chris Holtz