That can be changed to "search for user by e-mail address", which is partially coded.
Speaking of which, would you like me to fix that up, or have you been working on it? I have a bit more time now.
Riley ,'Potential'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
That can be changed to "search for user by e-mail address", which is partially coded.
Speaking of which, would you like me to fix that up, or have you been working on it? I have a bit more time now.
Jon, I haven't touched it.
OK. So as I recall, you could live with the black-box functionality of what I wrote, but you didn't like that there were two calls to the database. So it's the latter thingie that I need to correct?
And a search box for e-mails should be added.
So two drop down lists (email ---> userid and vice versa), and a search box?
I'm not against it; just want to make sure I understand.
No, no drop down lists. Two listboxes (though I still question the second one, but methods are methods), and a search box.
Sorry - I meant to say listboxes.
Another reason a listbox is useful is that sometimes the "from" address in an email will be slightly different from the profile email. e.g. maybe there's an added subdomain. Using a searchbox wouldn't give a match; If you used the listbox, you'd see the desired email near the one you thought you were looking for.
But the search doesn't have to be exact.
It's of no matter. I'm not the only one using it, so it doesn't have to cleave to my methods.
cleave
- snerkle.
running away.
Depends on the browser, Robert. Not all allow [user stylesheets].
Well, sure, but some browsers ignore stylesheets altogether.
(I spent an hour last night trying to figure out all of the CSS2 tag proximity indicators, the >s and #s and such. Headache.)