I'm not 100% sure, but I'm pretty sure that this is a known issue that has been resolved in our upcoming SP1 (Service Pack 1) for VFP 8.0. We are finishing up SP1 for VFP 8.0 next week and should have it on the MSDN web site for free download within two weeks.