Hi Gary.

When the newer version doesn't do what its supposed to and until MS fix it or provide a workaround. I reported this problem in October last year and the = workaround wasn't forthcoming until after SP1 proved not to fix it either. So, that application had to run in VFP 6 because it *wouldn't* run in VFP7

Aaaahhh! NOW I understand. Sorry about being so dense < s >.

This IS a real problem: how the bugs change from version to version. And I'm not talking only about VFP either. It seems that when I upgrade software that I have written, I inevitably change some of the bugs < s >.

Did you get an explanation about what caused this problem to pop up in the first place? Just curious...