Well, life doesn't always go according to plan! What the fork! - Epilogue to this sorry saga. What I interpreted as a some crud in the program was actually a WAD. So naturally, to clear the crud, I killed the update the workstation then restarted, then killed it again then rebooted the workstation and restarted, then killed it again and then tried to update it from the server and finally killed it at the server, rebooted the server and tried again. No luck so I posted here to see if someone else had experienced this. Luckily
@Beth Bowers had the fix and life moved forward. Then the ACH file was hosed. Fixed that. Then client reported that the 401K contributions were 5X what they should be. So I looked at one of the 35 employees check history and noted (unhappily) that Sage had created five check entries (all the same check numbers). At that point, I threw in the towel and asked the client to restore PR from last Friday so we can run the weekly PR from the start. Just too many tables involved to fix manually. At the very least, why can't the programmers insert a pop up panel stating to the effect that this may take some time as we have to void 80,000 (insert a number here) checks? Now THAT would be a WAD. Or perhaps do a better job of restarting the interrupted program update at the correct spot..... Happy Friday!
------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------
Original Message:
Sent: 04-23-2020 14:11
From: Jeff Schwenk
Subject: v2019 ADV PR2.2 Update
Fixed the ACH file (TY @Beth Bowers), cleaned up the bank rec for the duplicate checks (4/employee) still have to fix the bank account table as it thinks PR is still in progress (GLWSKA??). Little puzzle about why it is voiding checks? Where does it write the information? There is no check history table per se for PR.
------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------
Original Message:
Sent: 04-23-2020 13:01
From: Karen O'Lane
Subject: v2019 ADV PR2.2 Update
Yes, this is great info!! One of my customers had unfortunately managed to create a check number gap of about 300 checks. When they updated the payroll check register, it took over 6 hours, even running it directly on the server. Being able to create the direct deposit file came down to the wire; just 10 minutes to spare. Not sure how long the update might take with 80k checks, @Jeff Schwenk!
------------------------------
Karen O'Lane
Accounting Systems, Inc. (ASI)
Fresno CA
803.252.6154 x242
559.577.4142
90Minds Treasurer
Original Message:
Sent: 04-23-2020 12:31
From: Jeff Schwenk
Subject: v2019 ADV PR2.2 Update
OMG - @Beth Bowers @Andy Adkisson - I am going to nominate you both for the 90M support person of the week!!! This may even put you in contention for the support person the YEAR!!!! Client had mucked up her check sequence so Sage wanted to void about 80K checks.
Now all I have to do is fix their ACH bank file as it has about four paychecks in it......
------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
Original Message:
Sent: 04-23-2020 11:12
From: Beth Bowers
Subject: v2019 ADV PR2.2 Update
Check number gap issue? Have found this work around, thanks to @Andy Adkisson - Edit GL_Bank.m4t field 16 to field 15 minus 1
------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625