Hi Sherm


I'm surprised that it works in the Task Suffix. I would be concerned about
its reliability, as the records contents cannot be guaranteed in TS. The
way I do it is to just as you are doing, but with a Group Suffix on the
primary key, and updating the parameter in there. As you will know, the
record's values are always available within the Group Suffix, so this way is
definitely reliable.


And the reason it works is that when there is an identity field in the
dataview (I think as determined by the text 'IDENTITY' in the column's SQL
Type property), Magic adds a 'SELECT SCOPE_IDENTITY' to the insert
statement, and updates the column in its internal storage with the returned
value.


Mike Bannon

DataFormation Ltd., UK


From: magicu-l@... [mailto:magicu-l@...] On Behalf
Of sherman levine
Sent: 22 July 2013 22:18
To: magic maillist
Subject: [magicu-l] mssql autoincrement primary key -return value of new
record



I have an MSSQL "transactions" table with an autoincrementing integer
primary key field "TransactionNumber".
Magic 9.4

My "add record to transactions table" program is batch modify, no
primary table, exit/yes/after with a link create to the transaction file.

I can update a parent field (or passed parameter) with the new record's
TransactionNumber in the batch task's task suffix (although I can't do
so in the record suffix, presumably because TransactionNumber has not
yet been assigned by the database.)

Is using this method safe and reliable for determining the newly created
record's TransactionNumber?
I don't really understand why it should work, even though it seems to do
so in testing here.

Thanks

Sherm








------------------------------------

Yahoo! Groups Links

Sherm,

You and I remember the days when the record view was accessible from Task
Suffix, but ever since Magic PC 3.0 or so we've had to live without it --
even when examination shows it's really there.

In any case, I always use a Group Suffix in these cases, just to be sure the
data view will always contain what I think it will.

As to why the autoincrement column's value shows up, I imagine that happens
when the engine re-reads the row to make sure no other user has updated it.
Does that change depending on the lock mode?

Andy J

-----Original Message-----
From: magicu-l@... [mailto:magicu-l@...] On Behalf
Of sherman levine
Sent: Monday, July 22, 2013 5:18 PM
To: magic maillist
Subject: [magicu-l] mssql autoincrement primary key -return value of new
record

I have an MSSQL "transactions" table with an autoincrementing integer
primary key field "TransactionNumber".
Magic 9.4

My "add record to transactions table" program is batch modify, no primary
table, exit/yes/after with a link create to the transaction file.

I can update a parent field (or passed parameter) with the new record's
TransactionNumber in the batch task's task suffix (although I can't do so in
the record suffix, presumably because TransactionNumber has not yet been
assigned by the database.)

Is using this method safe and reliable for determining the newly created
record's TransactionNumber?
I don't really understand why it should work, even though it seems to do so
in testing here.

Thanks

Sherm



------------------------------------

Yahoo! Groups Links