A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Separate PK in Jxn Tbl?



 
 
Thread Tools Display Modes
  #221  
Old February 1st, 2008, 06:16 PM posted to comp.databases.ms-access, comp.databases.theory,microsoft.public.access, microsoft.public.access.tablesdbdesign,microsoft.public.sqlserver
Marshall[_3_]
external usenet poster
 
Posts: 20
Default Separate PK in Jxn Tbl?

On Jan 31, 4:59 pm, "Brian Selzer" wrote:

Constraints should always be checked by the DBMS, not by applications. If
you have two separate applications that manipulate the same table, and one
enforces one constraint while another enforces another, then all you need to
do to bypass one constraint is to use the other application! What, then, is
the point of even having the constraint?


I think that application constraints and database constraints are
really
two entirely separate things. The fact that they may be structurally
identical obscures and confuses this point. (Hence Brian's entirely
reasonable rhetorical question above.)

What, indeed, is the point of having one application and not another
enforce a constraint, *if we view this from the perspective of the
requirements of the database* Clearly there is none. However
individual applications may have requirements that are best
implemented as constraints *within the application.* I call these
"application constraints" because they are specific to the
application. They are *not* integrity constraints, even if we
are using identical mechanisms (in different locations) for both.


Marshall
  #222  
Old February 1st, 2008, 07:52 PM posted to comp.databases.ms-access,comp.databases.theory,microsoft.public.access,microsoft.public.access.tablesdbdesign,microsoft.public.sqlserver
James A. Fortune
external usenet poster
 
Posts: 903
Default Separate PK in Jxn Tbl?

Marshall wrote:
On Jan 31, 4:59 pm, "Brian Selzer" wrote:

Constraints should always be checked by the DBMS, not by applications. If
you have two separate applications that manipulate the same table, and one
enforces one constraint while another enforces another, then all you need to
do to bypass one constraint is to use the other application! What, then, is
the point of even having the constraint?



I think that application constraints and database constraints are
really
two entirely separate things. The fact that they may be structurally
identical obscures and confuses this point. (Hence Brian's entirely
reasonable rhetorical question above.)

What, indeed, is the point of having one application and not another
enforce a constraint, *if we view this from the perspective of the
requirements of the database* Clearly there is none. However
individual applications may have requirements that are best
implemented as constraints *within the application.* I call these
"application constraints" because they are specific to the
application. They are *not* integrity constraints, even if we
are using identical mechanisms (in different locations) for both.


Marshall


I think you're on to something. Making a distinction between database
constraints and application constraints helps me clarify my thinking.
Being able to "reflect" database constraints to keep applications in
synch with changes sounds like a great idea.

James A. Fortune

  #223  
Old February 8th, 2008, 03:11 PM posted to comp.databases.ms-access,comp.databases.theory,microsoft.public.access,microsoft.public.access.tablesdbdesign
Gerry Hatrick[_2_]
external usenet poster
 
Posts: 2
Default Separate PK in Jxn Tbl?

"Frank Hamersley" wrote in message
...
Keith Wilby wrote:
"Frank Hamersley" wrote in message
...

provision of a menu option to reattach a data .mdb!


Is it just me or is that complete gibberish? Reattach?


Just you mate (at least I hope so or we are doomed).

Pray tell how do you distribute new versions of "code"?

Never had that concern? - always just hacked the live .mdb?

Gawd.


No, you have a development copy of the front end, there's no "reattaching"
of code, you just make a new version of the front end available - front end:
code and all other objects except the tables. Gawd, gibberish indeed.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 07:03 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.