>I appreciate the advice. I realize that having a foreign key is sticking my neck out. However, this is a situation where I'm the third programmer on a massive project and changing the way the data is querried to be displayed means a total re-write of the entire system. (I won't bore you with the details, nor do I have the time to.) I was just wondering if there was a way to keep the foreign key updated without having to re-INSERT the records everytime the data changes. Anyway, I'm not using it for anything 'mission critical'. (mostly for displaying in a browse)
>
>Anyway, I thought it was a tricky route, but the only one that would fit in this monster app.
>
>Thanks again.
>
Tom,

I hear your concerns, but I can only quote a very wise comment that was once given to me, "It will NEVER be easier to fix this problem and you will eventually need to fix it."