Uwe Grauer wrote: > Paul McNett wrote: >> Sibylle Koczian wrote: >>> Yes, if there is a function producing the PKs you want. Not quite so simple >>> if >>> you invent each one (abbreviations for example). In that case the value >>> would >>> come from some control in the form, and I don't really think myFunc should >>> have to know about the UI. I will play around with this and see where I get. >> No, the biz shouldn't be aware of the ui at all. If it were me, I'd keep >> the PK invisible from the UI (and keep it meaningless), and just define >> another field for the abbreviation field that may well be unique but >> isn't *the* pk. > > This is always the better way to handle it - except for cases where > you can't change the data structure of a already existing database.
It is especially fraught with danger if the user is allowed to change the PK value for non-new records. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
