Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Unique id for executable.
Message
De
28/12/1999 15:04:39
 
 
À
28/12/1999 14:59:19
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00309394
Message ID:
00309413
Vues:
24
>Hi Ed,
>
>>What kind of a constant? If you need a completely guarenteed unique identifier, generate a GUID using the Windows API and then store it somewhere, but that's a large (16 byte) value. If it's generated per machine, then save it in the registry, otherwise, you'll need a table or initialization file to draw the value from at runtime.
>
>It is simply a two character code identifying the organization. I though I could do it using the Config file but I couldn't figure out how. Is that what you mean by initialization file?

You need something that you can read at program startup and save - it doesn't matter so much what the file is, as much as (1) it exists somewhere that it can be found and (2) it can be read by VFP. A simple text file with a known name at a known location would work fine; read it (you can use the low-level file I/O functions if nothing else looks interesting) and stick it in your application object or some other known place that everything will reference.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform