Hi Jos.

Seems this problem was a bug in VFP 8 to do with Tableupdate not respecting Rushmore in certain instances for Views.

SP 1 fixed it.

Regards,

Gerard

>Gerard. One change that might be affecting you in VFP8 is the SET TABLEVALIDATE TO command which by default does some table integrity checking. You can try setting this to 0 to force the same behaviour as previous versions.
>
>And of course you really should try to match the SET FILTER expression with an index if possible.
>
>
>
>
>>Hi.
>>I have just upgraded fron vfp6 to vfp8 and noticed, particularly across a network, a dramatic slowwdon in speed anywhere I have a set filter to on a file.
>>
>>I know I can look at optimizing the code (by putting in indexes etc) but does naybody know if there was some change in using set filter.... saving transactions have slowed from 2 seconds to 16 seconds.. and the only other change was upgrading from vfp6 to vfp8
>>
>>regards,
>>
>>Gerard