fenway

Preferably with a ID DESC... ;-)

No problem... sometimes I've seen selects followed by updates (like moving a balance) and it just doesn't work without some extra precautions.

Then why have it there?

Doesn't it have to? I'm quite confused... there's a plaintext string, and then there's the key -- they have nothing to do with one another.

With an ORDER BY clause... how do you mean?

I simply mean that depending on what you're doing with this afterwards, you have to remember that anything can happen between statements.

It means there are a lot of extra check to do for every update/delete operation.

How do you mean?

Hey, I only ever claimed that I knew nothing about PHP... ;-)

An UPDATE statement with an appropriate where clause?

Hi paul... long time no see! Not elegant? That's the only way to add values.

More to the point: alert(parseInt("010")); // alerts 8 Octal prefix magic is automatic.

Or function replaceStuff(str){ return ( str.match(/^[a-zA-Z]+$/) && str.match(/ /) ); }

Careful using parseInt without a radix.

<td valign=top align=right> doesn't work?

Hold on, does that mean yes? I think we're exploring a whole new area of fenway expertise here. I used to respond to posts frequently in the HTML/JS and (less often) CSS forums... I just can't keep up with the sheer number of topics.

Agreed... but if you have a paying customer, I'm not sure that they'd be interested in your learning curve. Regardless, if you need any help with design further to your original post, let me know.

No need to re-invent the wheel, that's all I'm saying.

Go right ahead... but just consider the timeline for the project.

I didn't know IE ever respect such attributes properly. Fenway knows CSS? I see possibilties. Just because I refuse to use CSS3 crazy selector thingys doesn't mean I haven't been building websites for a decade ;-)

I assume you're dealing with a proper database here.... and that you have a table of topics and a table of posts. But seriously, there is plenty of good forum software out there... why roll your own?

You mean "num" is the ID and seller is the ID from the clan/players table? If so: SELECT p.num, p.clan, m.* FROM players AS p INNER JOIN market AS m ON ( m.seller = p.num ) WHERE m.time<=$time AND p.clan=$users[clan] I'd rename "num" as player_id and seller as seller_id (or player_id) to make this more obvious. Also, make sure to quote those literals.

How are these two tables related?

What do you mean by overview?

I'm talking about one record per POST... some all of the post goes into a single field. Two people = 2 posts.