>>
>>All of the ways that I thought of were horribly inefficient, but I'd be happy to hear your ideas, if only to make sure they aren't the same as mine.
>
>Well, I am sure you've explored all of the options. I do have a question: When you say "horribly inefficient", how long does your SAVE TO replacement take? And how long does your RESTORE FROM replacement take? In my opinion, if it takes a few seconds, that is inefficient. But, not a big enough deal to stop using a product.
>
>If I understand correctly, you can't use VFP 5.0a and you can't use VFP 6.0...what are you going to do?
>

We're hoping for a fix from Microsoft (unlikely, but we've been told that it is possible), and if we don't get that, then we will be forced to redesign that part of the application to not use SAVE TO/RESTORE FROM. And for a replacement to be acceptable (due to how often it is called), it would need to take tenths of seconds at most. A few seconds would not work.