But then only one of the fields would be in alphabetical order, or do I misunderstand you?
asort()
should work less intensively than two separate sets of queries.
'Unleashed'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
But then only one of the fields would be in alphabetical order, or do I misunderstand you?
asort()
should work less intensively than two separate sets of queries.
I'm not familiar with asort(), but I'm guessing there would be a button or buttons on the page that would re-sort by either field? Kind of like the original page I designed a month or two ago?
No -- same page design, but the current code loads two 700+ pick lists with two separate sets of jaunts to the database. I do not want to do that. I understand that a pick list is mandatory for the user IDs, and will cave on the e-mail addresses), but we can grab the info for both lists in just one set of hits on the database, instead of two.
OK, I think I see what you're saying. I'd have to check at home to see exactly how I coded it to be sure I get it. I put in two separate SQL queries? Bad Jon!
Two separate functions -- one per list.
Right. I remember now. Do you want to hold off on implementation, or were you planning to recode it? I won't be able to get to it probably until late next week.
I'll give it a shot if I have time this weekend.
thanks ita! I was away and am going away again in 3 hours so sorry for the delayed response.
Hey you know what would be cool for the search engine? If we could search for posts by so-and-so or about such-and-such within specific DATE parameters. Don't you guys agree?
P.S. Thanks for all your amazing work, y'all.
Just had a server error, Server Not Found, about 5 minutes ago.