Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Avoiding Dublicate Field entries in a multi-user applica
Message
De
20/02/1998 13:23:20
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
 
 
À
20/02/1998 13:12:54
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00080125
Message ID:
00080152
Vues:
39
>
>Most programmers end up using something on this order. I have a different situaton where I have independent installations that may want to merge their data. I use SYS(3) to generate keys. One draw back is the number is nonsense and sometimes you would like to know the order records were added for audit purposes. Do you know of other draw backs to using sys(3)?
Hi,
I don't use it at all so don't know much about it. It ensures a unique filename, and use 8.3 format giving the name part. I know that it doesn't give a unique name on a fast computer. And I don't know what it uses to generate it (just check if one already exist on the current dir ???). If it doesn't use datetime somehow then the order wouldn't be reliable. In fact in a nonbuffered table recno() itself give the order. In a buffered table sys(2015) could do it if all workstation times were preset precisely. I even use sys(2015) to generate a unique filename
munique = sys(2015) 
mfilename = "T"+substr(munique,1,7)+"."+substr(munique,8)
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform