>I have officially fallen into the twilight zone. All of the workstations here run the main app from a loader program that copies the exe from the server to the local drive and then runs it from there. I have found two workstations for whom the latest menu definition works. Their exe compile times are identical to the version on the server, but the copy of the program on the server shows the old menu. From one of the workstations that works correctly, if I run the exe on the server directly, it does not work. So I copied the exe from the local drive (the one that works) back up to the server drive over the broken one. Run the server version, and it still doesn't work!!!
>
>this led me to believe that it had to be something in the foxuser.dbf files, so I deleted the foxuser.dbf files on the local drives. I have now found that running the program directly, instead of using the loader program, it works right. Keep in mind all other recent changes to the exe are showing, just not the menu.

Hi Erik,

This officially qualifies as perhaps the most bizarre series of events (connected with programming) I've ever heard of. We've all (or at least some of us, including yours truly) been down the road of not having the program buffer cleared causing problems, but this has gone from the sublime to the ridiculous. This has to qualify you for some sort of special UT award (Most Bizarre Problem?)

I can't figure out what could be doing this, unless the old programs were somehow cached on the disk. But that's so far out...maybe we all should start looking at other lines of work. (for me, an exciting career in the Food Services Industry):-)