Order No question

[vbajock]

As Macola issues order numbers, I assume somewhere a point is going to be reached when the order number rolls back around to 1. If an order with the number 1 exists in the History file, will this cause a key violation error when the order is posted to history?

 

[AKPolarBear]

The O/E number limit is 8 places or 99,999,999. Since Macola limits the history files to a maximum of 3 years, it is probably a moot point since you would have to write more than 33,333,333 million orders per year average to reach that number. Technically, I believe you are correct, it would.

 

[vbajock]

I had thought it was 99,000 or 999,999. That may have been true at one time. So, technically, I could pull a block of one million order numbers at the high end of the scale and reserve them for an app that issues its own order numbers, which then could be uploaded from the app to Macola without fear of key violations, at least until I was long dead, if the copy wrote 100,000 orders per year ?

 

[AKPolarBear]

I would consider pulling the numbers from the low end for your app and start the Macola sequence after those. They should never catch up with each other. Also, you might use a different number series and tie into Macola through a user defined field or some other unused and available field.
Then it should never be an issue. Just a thought.

 

[MacolaHelp]

There is only the 8 digit limitation to order numbers in the history file. I have some clients with 10 years worth of history. If you, however attempt to create an order inside the generic macola interface with a number that exists in history, you will be stopped & a message given that the order number exists in history. If you loaded these orders externally, they might indeed post all the way through to history, but your consolidated OE views would be trashed. This happens in generic macola today if there is an active Q type order and the same order number exists as an O type order in history. It has supposedly been corrected in 7.6.200 & will occur even though the key in active & history is a segmented key consisting of order type AND order number. You'd just have to load some data into a test db & see what happens if you duplicate these fields externally.

 

[dgillz]

I believe you would get the key errors you are concerned about if this happened. If this is an issue, purge history and you should be fine.

Speaking of history, there is no 3 year limitation on history.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[AKPolarBear]

No 3 year limitation on the history file? Darn, that’s why we have an ex-var and a new var!

We also purge ourhistory based on the ex-var’s advice. That will now be revisited. Thanks for straightening me out.