I have been tearing what little hair I have trying to find a fix for my remote view problems. Using Server 2003 and SQL 2000, I am working with Visual AccountMate, written under VFP6, and was having a devil of a time with modifying remote views. When I go to modify the view in the view designer, without making any changes and save it I get the dreaded "base table fields have been changed" message on every single remote view. In fact, not only were there NO structural changes, but the fields are explicitly declared (SELECT field1, field2... vs SELECT *...).

If I open a database and issue the MODI DATA command so I can see the views then modify most any view (especially those with memo fields), and without making any changes I save it, I get "the message" and the database object changes to show the following fields which are, I think ODBC parameters (SCOPE, COLUMN_NAME, DATA_TYPE, TYPE_NAME, BUFFER_LENGTH, DECIMAL_DIGITS, and PSEUDO_COLUMN).

The remote views all have the same properties that are somehow triggering the problem.
1) Shared Connection
2) Fetch all records
3) Parameterized (Field = ?gckey)
4) Update all fields

Most of the time, I could do nothing but restore from a backup. I tried refreshing, compiling, manually packing the database and even recreating a new database from scratch.

After trying everything under the sun, I decided to try changing the memo blocksize from the default of 64 to 1024 and packed the database. For some reason, this lets me get around the problem. Although I still get "the message" after saving the first time, if I go to the "Update Criteria" page and save it again. The ODBC fields in the database view go away and it seems to save OK.

I also tried this under VFP7 and it gave me the same problem before changing the block size. However, under VFP8, there is no problem.

Has anyone else had this problem?

TIA,