Complex (for me) custom counter question....

[Fletcher]

Thanks Bruce, I understand how a PK works and how the tables link.
What I am looking for is something that distinguishes the PK in one
process table from the PK in another process table. Since the three
process tables are linked to the same measurement tables, they can't
all have an autonumber PK. For example, if the three process tables
had the a value in the PK of 7...how would an entry in MeasurementA
linked to the number 7 distinguish between processX and processY? To
fix this, I wanted to create a unique primary key with a combination of
a cutsom counter and a process abbreviation. I have figured out how to
do this, but you have told me that there is a better way. If you can
explain how to better to this, I would appreciate it greatly. I am
always in search of new (and especially better, more effecient) ways of
doing things. A life of learning for me.


Thanks,
Fletcher...

 

[david epsom dot com dot au]

The custom counters are applied across several databases.
That is why we use still use a custom counter. But originally
custom counters were designed that way to handle high
concurrency data entry (search for 'high concurrency on
the MS web site)

I mention the manual process because, if you can't use
DRI, as we can't in this case, you should be prepared
for possible errors.

(david)

 

[Jamie Collins]

search for 'high concurrency on
the MS web site

Concurrency? Yeah, I think I've heard of that. Legal tender among
prisoners, right ;-)

Jamie.

--