..snip... > Why does it need to be any more complicated than that? I always seem to be able to complicate my methods. You should see the query I didn't talk about, I'm sure you would cringe.
> - never allow your keys to have any meaning (i.e., User_id should simply be > an arbitrarily assigned value) I have to admit to being self taught and I haven't gotten around to finishing my big thick book on data modeling. I have been consitent with keeping my keys "meaningless" and my tables normalized, I'm just going nuts on this project trying to do to many things at once causing these momentary lapses :-) > - a foreign key (which User_id in the tblDocApprove table should be) must > have a matching entry in the primary key of the related table (does the > Administrator actually have a User_id of 0?) Errrr, no. > Please feel free to ignore all of that. I'm just a big stickler for what I > consider to be proper database design, so I felt a need to point that stuff > out. Good advice shouldn't be ignored :-) Thanks for all the help : David Nesbitt : Web Developer (ColdFusion) : Tundra Semiconductor : Ottawa, ON Canada : [EMAIL PROTECTED] - You are subscribed to the CFUGToronto CFTALK ListSRV. This message has been posted by: "David Nesbitt" <[EMAIL PROTECTED]> To Unsubscribe, Please Visit and Login to http://www.CFUGToronto.org/ Manager: Kevin Towes ([EMAIL PROTECTED]) http://www.CFUGToronto.org/ This System has been donated by Infopreneur, Inc. (http://www.infopreneur.net)
