for a stand-alone VFP solution it'd probably not worth the trouble, for
a SQL back-end // where agents other than your program might get access
// I like to use pk; fk constraints; mostly deny access to the base
tables and provide user views barricaded with 'instead of' constraints
that validate insert / delete / update transactions with logging. The
hope is that even illegitimate users can only do 'proper' transactions
and at worst can be traced.
On 01-Nov-2017 1:56 AM, [email protected] wrote:
At the day gig, they use FK constraints and References in their Oracle
database schema. Honestly, I got into that years ago with VFP but
then kinda fell off that wagon over the years, preferring to just
handle some things in the BizObj of the solution rather than put more
rules in the backend database. The idea was that if I changed backend
databases, I wouldn't need to rewrite a whole bunch of specific DBMS
code.
Where's your preference in design with these in mind?
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
