>>Why no have 3 tables: >>Members >>Data >>TheseMembersAreOld
>>Members and Data are as you have them defined. TheseMembersAreOld >>contains only the Member_ID field. >>You then make the Member_ID field primary key on TheseMembersAreOld and >>Members. You can then perform a very fast joins. >Hm, thank you for the idea... I think my problem is the OLD members and >members are not the same people. That is why I have renamed them (added >100000 number to every one of them), so Data table now has >numbers from 1-1000 (my new members) >numbers from 100000 to 101000 (my old members). >From old members I only need the name, nothing else! From new members I need >all the data. >Now because in the forum topic (yes, I am builing a custom forum) there must >be a member, I need >1. If this is an old member from the old forum to disply only name >2. If member is new to display all the data. >Now I have a problem of joining the 3 tables because obviously in Data field >Member_ID there is a number that represents a member OR a number that >represents a old member, never both (none is the same). In SQL I can not do >the AND and compare both MEMBER_ID's because it would never return anything. >If I use or I do get data, but not one, but multiplied number od times (every >new member is then resulted or every old member, depending on in which table >SQL finds the data). >Yours >Jerry >Slovenia --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
