Hi Michael,

- try set SET TABLEVALIDATE TO 0
- check COLLATE of all indexes if equal to VFP COLLATE
- check CODE PAGE of tables if equal to VFP Code Page
- if you use function in index expression, like as STR() change to STR(n,length) - key must has fixed length

MartinaJ

>I have an application that has been updated from VFP5 to VFP9. One of the screens has a number of set relation commands in the load event.
>
>Using the coverage profiler, this is where the code is slowest.
>
>Is there a difference between the way VFP9 and VFP5 process the set relation command?
>If there is, is there a work around to speed it up?
>This screen, is very slow to load in VFP9, and very fast in VFP5.
>Needless to say, this makes for upset users... <vbg>
>TIA,
>Mike