||Re: Record lock for unique #
||Mon, 25 Mar 2019 11:19:21 -0400
I have switched from using a common table to keep track of sequential
numbers to using a common INI file.
The speed at which Windows can open and update a INI file is lightning
compared to opening and updating a table.
No record locking involved, Windows handles everything.
As a bonus by editing the INI file with a simple text editor, I can change
the stored value very easily.
I use my own read/write INI routines but you can use the INI.cc from the
set procedure to :dUFLP:Ini.Cc additive
oMyINI = new INI(set("dire")+"\Podium.ini")
key_no = val(oMyIni.GetValue([Config],[key_no]))+1
close proc :dUFLP:Ini.Cc
"Randy Waldman" wrote in message news:qZ87mFr3UHA.2848@ip-AC1E04A7...
Plus 12 user. Several users on same program. Each one has to frequently
grab a unique sequential # from a common table. Do I need to code a "record
lock" or will dBase take care of (possibility of dupes) on its own? Thanks,