Quantcast
Channel: Best Method
Viewing all articles
Browse latest Browse all 5

Best Method

$
0
0

I have a table with 5 fields that I am concerned with. 

I was going to concatenate the data in those five fields to create a new field.  I was going to make this new field the primary key, as that concatenation will create a unique value that will never be duplicated.  However, in a separate post, it was strongly suggested by many, that this was not a good Idea.

What I need to do now, is assure that when a user creates a new record, s/he does not cause a duplicate record to be created. 

I was going use the after update event to create my concatenated new primary key and see if that key already exists.  If it did, I would not allow the entry.

Since everyone suggested that my primary key was not a good idea, I don't have any idea how to do this check.  Any suggestions?


Viewing all articles
Browse latest Browse all 5

Latest Images

Trending Articles





Latest Images