Re: Applicants and Subtypes

My homework days are long over, thanks...

You are right in considering some other way of looking at the problem. Entering data redundantly is not a (good) solution, but sometimes it is unavoidable from a business prespective. In this case, unless you are using some sort of (expensive) data mining tool to do fuzzy checking of your data in the hopes of linking up the matches, your only other hope is to find some sort of ID that will eventuallly also be the student's ID. Of course, because you are working with international studnts, you can't use SSN. Soooo, unless you can get them to use your internally-generated ID on ALL correspondence, you're stuck with redundant data.

<leroyg_at_my-deja.com> wrote in message news:883k85$vsb$1_at_nnrp1.deja.com...
> In article <87pb9d$olo$1_at_bob.news.rcn.net>,
> "Alan Shein" <alanshein_at_erols.com> wrote:
> > This looks like an elaborately hidden homework assignment, and I'm
 sorry for
> > saying that if this is legit, but anyway...
>
> It is legit (I work for a university), and for now the database design
> is not going to be changed. But I whereas the lgeacy system I described
> might need redesigning, the new one has more redundancies--separate
> name and address information for inquiries and applicants. I figured
> that there may be another way of looking at the relationships.
>
> Thanks for your feedback, though. This should definitely be a homework
> assignment. If you want me to write up the full design problem and send
> it to you to someone who does need an assignment, please let me know!
>
> Regards,
> Leroy
>
> --
> Leroy Gonzalez
> leroyg_at_my-deja.com
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Mon Feb 14 2000 - 00:00:00 CET