I have seen this, but I have been able to correct it by running DBSetProp on all the offending fields to correct the data type and size:

DBSetProp('myview.myfield', 'Field', 'DataType', "N(1)")

I have a PRG file where I keep a PROC for each view with code needed to create each view. I can then run any PROC to recreate or modify a view.

>Hi Mark.
>
>>Does this happen with every view? -> Yes.
>
>What if you predefine the parameter before you create the view? ->Still occurs
>
>What if you create the view outside any designer and just use code in a PRG to do it? ->See my further comments...
>>
>
>I rebuilt the pc again and I tried to be careful to test for the problem in between each software install and I thought I didn't have a problem any more.
>
>But, its back. Ugh! Well, sort of. I have discovered a few things ... and perhaps there is someone who may know where my particular problem is coming from.. The error is coming up still ... that the base table fields have changed and no longer match... but I can still save the remote view and it works ok. Weird!
>
>The problem appears to be in the remote view designer or somewhere underneath it, perhaps.
>
>What I notice is that when I go into the properties button on the fields page of the remote view. ... the field sizes are wrong on a lot of fields .. but not all. Character fields that are 25 30 and 40 chars in width, say they are 20 chars. (Or is that normal ... I rarely go into that dialogue?)
>
>Consequently, it would seem that when I try to save the remote view .. I get the error message as the fields are different between base table and view fields? Maybe?
>
>Ever seen this?
>
>I have installed VFP6 and VS SP5 My ODBC is version 3.520.6526.0
>This problem is occuring for my using SQL w/odbc accesing either an MSDE SQL database and I also found the problem occurred when accessing a MS SQL 6.5 database.
>
>Could another software piece I installed have caused a problem at a lower level?
>
>Thx, Scott