Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Stop caching the $#@% menu!!!
Message
General information
Forum:
Visual FoxPro
Category:
Menus & Menu designer
Miscellaneous
Thread ID:
00159328
Message ID:
00159517
Views:
35
>>Ok check this out. When I generate the mpr (from the menu designer-> menu -> generate menu option), it updates the file, but it appears that it is putting the server's timestamp on it, which happens to be about 5 minutes behind my workstation's time. When I COMPILE mymenu.mpr, it updates the mpx file with MY timestamp. So I have a compiled file that is newer than the source code. I haven't figured out exactly what is going on yet, but this is causing me major headaches.
>>I tested to see if MODI COMM was doing this with regular prgs, and it isn't. Both MODI COMM and COMPILE prg use my timestamps.
>>
>>I know a quick fix would be to coordinate my clock with the server's but this is ridiculous. Any insights?
>
>Hi Erik,
>
>That does sound odd, then again, I've heard of stranger.
>
>The quick fix is probably the best. I think that this (synching your clock to the net's) can be handled for you automatically with your login script (under Novell). I don't know about doing this from NT. I'd suggest that you get with the network administrator and see if this can be done, or if there's another solution.

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.
Erik Moore
Clientelligence
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform