Out of curiosity I tried that and both scx and sct timestamps were updated the same. I tried adding some code in the setup snippet. Both timestamps changed. I went back to the original scx and sct and moved a button and again both timestamps changed to the current.
Wouldn't it make sense that if the scx is the table and the sct the memo file that if a memo field in the scx is changed the scx would also be different?
I also assumed that the scx date would be updated at the same time as the sct. When I test this, is seems to work that way.
One theory I wanted to pursue, but haven't yet, it whether a 'Rebuild All' may play into this. My thought is that maybe if the environment changes (e.g. windows version, screen resolution, etc), that something might be updated during the 'Rebuild All'
I know that Report Files store the default printer at the time that they are saved. I wondered if screens did something similar.
Many of these screens are ones that haven't been changed in years. A comparision of them (I have source code control so I can compare prior sct's for a particular scx file with current sct's - when the scx date has not changed) with WinDiff suggests a code change, but I cannot see any difference.
I noticed this years ago and came to the conclusion that it had something to do with opening a screen file to look at (but not change) code. I was able to get an updated .sct timestamp only just now by doing the following:
1) Open project
2) Edit a screen
3) Double-click on a field on the screen
4) Click on the Valid button on the Field window
5) Click on the Edit button on the Snippet window
6) Click OK to remove the Field window
7) Close the Valid window
8) Close the scx window
9) Answer "No" when prompted to save changes
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.