>>What is a practical reason or application of having Resource=On in the Config.fpw for a VFP 9 application (executed by customers as .EXE file)? TIA.
>
>From
http://fox.wikis.com/wc.dll?Wiki~FoxUser>
>Fox User stores a variety of information, similar to the "property bag" concept of other languages. Some of these are very useful in an application, such as preventing the printing of reports from Print Preview, Hide the Print Button from the Print Preview Toolbar. It also stores:
>Windows preferences and positions
>Diary / Calendar data
>Toolbar configurations
>Most Recently Used (MRU) lists for IntelliSense
>
>SET RESOURCE OFF if you don't need this feature in your client's runtime environment (to avoid VFP Rookie Mistakes), or toggle on and off resource files for specific functionality, like custom toolbars above.
>
>The internal structure of the memo fields are not documented anywhere that I know of.
>
>Use SYS(2007) to generate the checksum for a resource file entry (or make it invalid for to ignore it)
>
>-- Ted Roche
>
Thank you! This is what I see in my application that the Set Resource On causes more problems at run time than benefits (if any). So I am turning it Off for my customers.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
