T
Tim Kuehn
Guest
I'm thinking that the FIND FIRST / WHERE structure is running into cases where there are multiple records in TT1 that match part of the WHERE clause and it has to scan multiple records to find one that matches both parts of the WHERE condition - though it wouldn't explain why CHAR versions of the same fields performs as expected. Replacing the FF with a FOR EACH / LEAVE may go faster - can you give that a try and see what happens?
Continue reading...
Continue reading...