Hi Fabio,

Apparently I didn't make my point clear enough (which I thought I had with the repro code):

1. We have an existing VFP8 application working on a bunch of tables, each has a candidate index (on field c1 in my example, with no filter), also an autoinc field (c2 in my example)

2. To prevent the documented (thus expected) "Field C1 is read only" error (VFP error 2088) when issuing any GATHER MEMVAR statement, we already have the AUTOINCERROR set to OFF in our application

3. Everything worked fine up to this point, until I decided to introduce an index filter "FOR !DELETED()" to the candidate index (on field C1 as in my example), then I started to get this "Data type mismatch" error (VFP error 9, not on field C1, but on filed C2). This is beyond my expectation because I can't find an explanation for this behaviour, why a seemingly small change to one field triggers an error on another (to me it's a totally irrelevant error).

Obviously your explanation to the issue ("C2 is a read only field") does not apply here, because I don't get that error (error 2088) in the first place. If the catch-all "SET AUTOINCERROR OFF" could do without the need of something like the "EXCEPT C2" part in every single GATHER statement, I'd pretty much appreciate it.

So the point is, if a TABLE change requires CODE change in a resonalbe way I can live with it, but in this case it does not appear to.