Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Any purpose to TIMESTAMP field in FRX's
Message
From
13/04/2006 15:54:12
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
 
To
13/04/2006 15:45:09
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01113217
Message ID:
01113590
Views:
20
>I have found times when a change is made in the form but the timestamp does not change (not updated). Create a form and add an optiongroup and save the form. Close and USE the form and note the record and timestamp of the optiongroup definition. Now close the form as table and reopen as a form (MODIF FORM ..), change the name of one or more of the options in the optiongroup. Save form, close and USE again. The timestamp does not change... even though the properties memo field entry has changed (the Name property is different for the option buttons).
>
>The project manager will still recompile the file since the form record time stamp has changed (as well as any cursor records). The timestamp does not always indicate where the change occurred.

Though I can't imagine where would this piece of information be of much use (since it's for PM's own use), it's still good to know. It seems the mechanism of checking what needs to be recompiled has changed over the years, and that timestamp isn't really as important as it once was - as it's not necessarily updated. Haven't checked this for a dozen years, so thanks for doing the research.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform