It's dead simple, and it works.  It does all history.  Sys database not affected.

We have seen data corruption from users posting number changes while others were working in the system, so we always recommend that everyone else should be out of Sage 300 when number change posting is done.  1. Everyone out.  2. Backup.  3. Post.  4. Spot check posted changes.  5. Normal work resumes.

Huh?  You can't even start this utility if anyone is logged in.  I have NEVER seen data corruption with this utility unless the hard drive crashed or the network went out.

So  I activated this Utility. Went thru the simple process of converting my AP account.

Received a splash screen after Post.

It began the process then got stuck on 14 of 65 Records, with the dialogue box "Not Responding". Noone was in that dataset other than me the Admin.

Anyway, I was getting ready to post this, when, "Not Responding" picked up again, and finished. Whew

"Not responding" does not mean "not working".

So  I activated this Utility. Went thru the simple process of converting my AP account.

Received a splash screen after Post.

It began the process then got stuck on 14 of 65 Records, with the dialogue box "Not Responding". Noone was in that dataset other than me the Admin.

Anyway, I was getting ready to post this, when, "Not Responding" picked up again, and finished. Whew

Just monitor using task manager. It does a LOT of work, can take even half a day on large databases and slow servers.

Yes all users must be out the whole time.