Here is a old thread on vb.com, http://www.vbulletin.com/forum/forum...e-is-ambiguous

OP thinks it was from a old mod, that did not remove the table when the mod was deleted.

OK, then the extra column is probably not being used. What you could try, since you know how to rename table columns, is to go to the *user* table and rename that column. Then if it turns out that something is using it, you'll still have the data. But if nothing else breaks, you can eventually delete that column from the user table, if you want.

Be extremely careful when making database changes. You should back up your database before doing it.

I have since fixed the problem, thanks a lot for your help!

What did you do to fix it incase someone else runs across the same issue?

My guess is that he renamed the status column in the users table.

In case people are unsure what the error means:
It indicates that both tables have a column called status but the WHERE statement doesn't specify which table to use for the status column.

And for future reference in case someone else stumbled upon this thread, how did you fix it?

Fixed the error by renaming 'status' from the user column as advised, the error seemed to go away entirely. Old script must have added it and not removed it upon un-install making the database confused at the two 'status' rows or whatever

thanks for your help!