MM 2.01 question

[ids]

This problem came up out of the blue. This store is still version 2.01, while the new store, version 4.+ is being completed.

Order numbers, all of the sudden are being re-used. So, info from old customer orders are being used instead of the new orders. The store, I'm told, has been stable for about 5 years -- until now. No known changes have happened including a backup restore. That is still being researched.

I know that when MM 2+ was released, I avoided it, As I did with 3. We had settled on 2.13 I think. I've also slept once or twice since then so my memories about this version(2.01) and problems/bugs have long been expunged.:p

Any of you other old timers have a recollection of order numbers getting re-used, what was the cause, and was there a fix?

TIA
Scott

[Kent Multer]

Offhand, I'd say that the most lilely cause is either a corruption of the StoreKeys database, or some other database glitch. have you packed the store lately? If it gets any errors while packing, that would be a clue. Also, check the StoreKeys record for Orders. And if the store's been around for a long time, it may be running out of hard-drive space; that sometimes causes weird errors.

Hope that helps --

[dotCOM_host]

The problem is most likely caused by deleting expired baskets while recovering order numbers in the process. It's quite common, unfortunately, and we see clients on v4 still doing it frequently (they finally fixed it in v5). I don't recall if v2 had that same option, I'd have to look for one of our clients' stores still on that version...

The good news is that to fix it you can simply edit the storekey database in a proper DBF editor and increase the order count to a value higher than the last good order (NEVER go down), then pack your store and domain files.

[ids]

Version 2.+ didn't yet have that option for recovering order #s. When you clicked on "delete baskets," it did with No questions asked. The storekey dbf must have been fixed becuase I haven't heard back. The storekey db was my first answer..for them to fix. They were very curious how it could have happened. I remember that there was a couple unstable versions of MM when 2.0+ came out and I/we personally waited until 2.13.

Regards,

Scott