Not really, that was just the only variable that I could think of. I had already ran vfpoledb.exe since I had seen something similar on a different thread and it didn't correct the issue.