Sage 100

4.40. The GL journal number is resetting to a number that was already used last month. This has happened for two months in a row. The GL Option for ""Reset Journal Numbers During"" is on ""Never Reset"". Was this a bug?

I'd check GL_options thru dfdm and see if the data field is set correctly there.

Agree with Roberta, there could be bad/invalid data that is displaying one way in options, and behaving another way in period end....

I've confirmed that the options show N via DFD&M. Any other ideas? I swear I remember something about this behavior, but can find nothing in my personal collection of KB articles, so I either didn't keep it, or I've lost my mind.

What changed that this would just start happening?

This is from the 4.4 Customer Upgrade Guide: ""Journal and register numbers are now reset separately based on the selections at the Reset Journal Numbers During and Reset Register Numbers During fields in the General Ledger Options window."" Are they both set to Never Reset?

In case DFDM has a bad, unseen character, go into it, edit the field, and manually type in an N. If that doesn't work, not that it's a great workaround, but you could you default to ""Year End"" and (assuming it will actually only reset at Year End) when they do their year end processing, part of the process is to change the next Journal and Register numbers manually. If this does work, it would at least give you a little time to figure it out (assuming year end isn't soon) and they'd only need to do it one time a year. Or, they could upgrade...

They're both on ""never reset"". And who the hell knows what changed? The customer certainly doesn't. Some people shouldn't be allowed to operate software. @RobertaChase - I will have them try both of your suggestions. I thank you all.

My questions is why are those ""Some people shouldn't be allowed to operate software""; usually MY CLIENTS? LOL

LOL! I suspect there's an epidemic, @MadelineStefanou

Some days I think there should be licenses, but then I drive somewhere and realize that wouldn't solve the problem...

Quick recap. I don't know why this happened to begin with, but resetting the Next Number in Source Journal Maintenance corrected the problem for manual journal entries. We had to reinitialize the GL Recurring data files and set up the recurring entries again, and then the newly generated recurring entries picked up the correct sequence number. All is well. Thanks, everyone!

Thanks for posting the resolution.