Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Strange SCREEN behavior
Message
From
07/10/1997 13:19:45
 
 
To
05/10/1997 23:03:25
Larry Long
ProgRes (Programming Resources)
Georgia, United States
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00052958
Message ID:
00053553
Views:
34
>>>>>>>>My office has an application in FPW 2.6a. We are using Windows 95 on a Novell network. We needed to add some comboboxes and checkboxes to some screens we have in a D_UDIAG.EXE file. This D_UDIAG.EXE is called by another
>>>>>>>>file called USMAPS.EXE. After we rebuilt the D_UDIAG.EXE, we ran our USMAPS.EXE and saw that the old screens
>>>>>>>>without the comboboxes and checkboxes showed up. So, as a test, we ran the D_UDIAG.EXE by itself. The new
>>>>>>>>screens showed up then. At this point, we rebuilt the USMAPS.EXE thinking that compiled copies of the old
>>>>>>>>screens from the D_UDIAG.EXE may have been included in it - an (excluded) reference to D_UDIAG is in our USMAPS.PJX. We still got the old screens after rerunning the rebuilt USMAPS.EXE.
>>>>>>>>
>>>>>>>>Does anyone have a clue as to what is going on? Our paths have not changed. We made sure there were no .SPX
>>>>>>>>files hanging around. Could it be a Windows 95/FPW 26a issue?
>>>>>>>>
>>>>>>>>Thanks,
>>>>>>>>
>>>>>>>>Dan Rhymes
>Scan your bosses computer (if standalone) for files like UGRP*.* If on a network scan the network for UGRP*.*. Maybe old files hanging around somewhere else.
>You did say that the wait window came up and the old screen as well?

Larry,

I put a WAIT WINDOW in the D_UDIAG.EXE to make sure we are hitting the .EXE it was supposed to hit. The WAIT WINDOW appears; so, I know we are hitting the correct one. However, when the D_UDIAG.EXE calls the appropriate screen, it is still finding an old version of the screen. And I can't find the old version - compiled, .SPR or .SCX anywhere.

As I said earlier, we are calling the screens like this:
IF SYSMETRIC(1) >= 800
DO (tcDialog)+"1.SPR"
ELSE
DO (tcDialog)+"2.SPR"
ENDIF

On entry to the main program in the .EXE we pass a subject name. Then we concatenate a "D_" prefix to it (D_ for dialog box). We are not tying it to a subdirectory path variable; i.e., DO (cSprDir)+(tcDialog)+"1.SPR". Should we do so? And if so, how does an .EXE handle that kind of call when the screen subdirectory does not exist? It would exist on the developer's network subdirectory but not on the users.

Thanks for your help.

Dan
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform