Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Foxuser versus Register
Message
From
31/05/2006 16:23:34
 
 
To
31/05/2006 08:48:46
General information
Forum:
Visual FoxPro
Category:
Installation, Setup and Configuration
Environment versions
Visual FoxPro:
VFP 7 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01126040
Message ID:
01126311
Views:
19
>Hi Peter.
>
>>I'd like to store a developer preference somewhere. Several options come to mind:
>>
>>1) In a memfile
>>2) In Foxuser.dbf
>>3) In the Windows Registry
>>
>>The first one is not my first choice in this case. The second one is the simplest and safest, I guess. But the documentation says: Modifying the READONLY field and/or deleting records from the resource file are the only actions you should perform on the FOXUSER file..
>
>Check out FoxResource.PRG in HOME() + "Tools\XSource\VFPSource\Toolbox". It contains a class for saving and loading settings from FOXUSER or any other resource file.

Doug,

Thanks for the reference. I regard it as an 'approval' afterall (from the foxteam) that the resource table can be freely used as long as that certain administrative principles are applied with care.

However, there is one thing that strikes me. Reading the code in the PRG (and in other PRGs in that same folder) reveals a different formula for the CKVAL calculation. In the code the formula is VAL(SYS(2007,DATA)). However, Calvin Hsia uses VAL(SYS(2007,SUBSTR(DATA,3))) and that is indeed the formula that creates the CKVAL value I found (in vfp7).
Groet,
Peter de Valença

Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
Previous
Reply
Map
View

Click here to load this message in the networking platform