>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
My guess it that you have made two copies of the screens, one for USMAPS and another for D_UDIAG. Go into the USMAPS project and look for the screen file name, if it is in there, check the files exact path under the INFO project option. Another possibilty is that the copy was made and saved under a different file name. How do you refer to D_UDIAG? Do you pass program execution to it by doing a DO D_UDIAG, or is it a procedure file that you refer to indirectly by SET PROC TO D_UDIAG?