full reload on page?

TCovert

This is my problem:

I have a page, that when you click on the "New Order" button, it goes out and inserts an empty record into the database, and then I have a query that retrieves the max of orderid. This will give me the orderid that will be used for this order.

Then they fill in their info, and submit the order. Then on the submit page, there is a link that returns them to the order page, to place another order.

But, when they return to the page, and hit "New Order", it gives them the same orderid as the last time. It doesn't insert the blank record in the database again.

If you do a force reload of the page, then it will get you a new number.

Why would this be? How do I fix this?

AstroTeg

Crazy question - what happens when 2 or more people place an order at exactly the same time? Do they get the same order ID? And if so, wouldn't that be a problem?

TCovert

This is an in house operation, and with the number of people using it, it is almost impossible for this to happen.

Any idea how to make it do the insert statement everytime?

AstroTeg

So when it does happen, you're ready to accept the consequences?

I'd suggest finding another way of generating an order ID. It may require you to change your process, but in changing, you will mostlikely work around the problem you're having of doing a blank insert. (I'd take a guess the table you're trying to blank insert into may not allow a field to be duplicated, although without the table specs, I can't say for sure.)

TCovert

But, if I do a force reload on the page, in the new order state, it inserts that blank record and gives me my new orderid.

AstroTeg

Need table specs and probably SQL queries your using to get a better idea.

Although I'd recommend creating order IDs based off of the time (and/or date) plus 1 additional piece of info (such as a customer/user ID). Then you work around the insert problem because PHP can generate this ID on the fly without querying for it.