Hey Nick Thanks.
Your comment about ">Why does the app have to throw an
error if the employee is missing - can't it just handle that?<"
got me to thinking.
first it ticked me off, then i realized what you where getting at.
so what i need to do is instead of deleting employee data when they a fired
from the Picture Board.
What i need to do is create a check box the for active/inactive.
so we can still keep the relationships in other apps, but also tell what
studio has laid off the most people & at what level of seniority is the most
secure.
just trying to quickly do one app is going to turn into 2.
HR, is going to like this.
thanks
-paul
-----Original Message-----
From: DeVoil, Nick [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 5:40 AM
To: CF-Talk
Subject: RE: db structure question
Paul,
>wouldn't it be just as fast to stick the actual unique value of the look up
table into the tbl_Mast_Table?
Yes it would. However, I find that using a unique autonumber ID for every
single table makes coding more standardised & therefore faster.
Don't quite understand your second point. Why does the app have to throw an
error if the empoyee is misssing - can't it just handle that?
Nick
**********************************************************************
Information in this email is confidential and may be privileged.
It is intended for the addressee only. If you have received it in error,
please notify the sender immediately and delete it from your system.
You should not otherwise copy it, retransmit it or use or disclose its
contents to anyone.
Thank you for your co-operation.
**********************************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
