I should add that you need to make sure the insert actually happened
INSERT INTO tablenanme.........etc
if SQLCode = 0 then
SELECT idcolname into vidvariable from tablename where count = insert
else
--handle insert error
endif
Dennis McGrath
Software Developer
QMI Security Solutions
1661 Glenlake Ave
Itasca IL 60143
630-980-8461
[email protected]
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Dennis McGrath
Sent: Wednesday, September 04, 2013 9:09 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: COUNT = LAST and Best Practice
COUNT = INSERT
Dennis McGrath
Software Developer
QMI Security Solutions
1661 Glenlake Ave
Itasca IL 60143
630-980-8461
[email protected]
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Bruce A. Chitiea
Sent: Wednesday, September 04, 2013 9:07 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - COUNT = LAST and Best Practice
All:
I understand from prior postings that 'COUNT = LAST' may mislead a user in a
multi-user environment. The actual 'LAST' record may be "someone else's" by
the time this user's routine hunts it down.
What's the best coding protection to ensure that the LAST I get is the LAST
I intend?
Thanks much,
Bruce Chitiea
SafeSectors, Inc.
eCondoMetrics
909.238.9012 Cell
