>>I found that when I designated a field as a
>>PRIMARY KEY. That the DBC would prevent me from
>>having any other fields with that same value EVEN
>>IF IT WAS CONTAINED IN A DELETED RECORD. That is
>>crazy and I do not wish to even hear of a
>>WORKAROUND for it.
>this is exactly the way is should work as deleted
>records can be recalled... - the primery key
>should be a unique key - i almost always make it a
>"random" or some other non-meaningful
>key - what u ask is good for non-primery keys
>
>>All of my systems are designed to build the
>TABLES
>>and INDEXES automatically when first executed.
>>They will also detect a need for structural
>>changes to tables and indexes each time they are
>>execut
>this can be done for a DBC as well
I am sure it can ... But as they say, the devil is in the details.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only