>Can't you just make a check before you make a call to the DB? >if( member_id > 1000 ) > // old member query here >else > // new member query here
Now I did just that, but that means I have to open recordset 20 times a page (for each record separately)... I am a begginer, I don't know if this is a speed defect, but I would think it is... Opening recordset 20 times and selecting one record instead of 1 time selecting 20 records... If penality is not much, I would take the solution, I don't have 1000000 users a day (only about 500). Actually I did something simmilar: I left joined the DATA with MEMBERS and in a loop when displaying records, when I see that the MEMBER_ID belongs to the old member, I open another recordset that get's me his name from OLDMEMBERS table. I thought that this is better than the first solution because when my database grows, all of the new messages will be from new members, not old, so the condition to open recordset in for...next loop would not be executed. Is my thinking valid? Yours Jerry --------------------------------------------------------------------- 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
