>Has anyone else experienced a problem with INDEXSEEK?

I'm not quite sure, but maybe. I have a loading program that imports data, and sifts through many GBs of different very large tables with the following type of code:

COPY TO (tablename) DATA (dbcname) FOR !INDEXSEEK(field,.F.,table,index)

It's not pretty, but in testing ideas it was by far the fastest. However, I have had occasional memory error messages running this section of the app. Not frequent, only occasional, and it may be due to something else, since there are a lot of very large files being shuffled around in this app. So, your theory is possible, I would say.