Hi Wayne,

Thank you for your interest in my issue. Sorry for taking so long to reply to you; I've been entertaining two sets of relatives this month.

The problem shows up usually as an application crash (GPF, Illegal Instruction, Dr. Watson error, etc.) when a form is opened that uses the table with the errant index (not even using the index tag that seems to be causing the problem). It is not always consistent between machines, and does not happen when simply opening the table interactively in VFP and browsing.

Doug has suggested upgrading to VFP 7 SP1 and that it may have been fixed there. I'm hoping to get approval of my company to do that.

We have had to alter the strings in the index field so that they begin with relatively unique character sequences. That seems to get around the problem, but not in a very user-appealing way. If you can think of any other workarounds, I'm open to them!

Thanks,

Jeff