Sage 100

Has anyone noted that the Paperless MOVE appears to have an upper limit of # of records? I was moving someone to a new server, new version and moving the Paperless and first tried the Relink in Utilities. That kept just going away - one second it would chugging along loading records and the next MAS wouldn't be running any more. So I tried going through the Viewers to move instead (luckily the old server was still connected) and decided to try GL year by year. I thought it was going fine then suddenly realized that then number of records successfully moved in 2011 was the exact same number as in 2012. Riiiiiight. So I pulled them back up and started scrolling and yep - only a portion were moved over. And the records are in journal number order, not date order, and they reuse journals. SO I had to go 2-4 months at a time to get them all moved. Spent about 4 hours JUST on Paperless, which is some of that mindless monkey work that makes you want to throw things.

Just spent two hours on a similar issue. This customer only had 3,400. Paperless is a great tool but it's stuck in the 2000 technology era. Moving it (which is a reality now that customers are upgrading servers, virtualizing, etc) is a REAL pain. Sage should create a folder and common naming structure and embed it in \MAS90 so that they can use relative directories.

The only thing about having it embedded in \MAS90 is that it takes so much time to copy for backup purposes and to move with each upgrade. We have changed it to a level above the MAS90 directory so we don't have to move them on an upgrade. Doesn't solve the new server issue, however.

I have a perform logic script I wrote to reassign PDF Directories to get around this (changing them on 40+ companies in small batches was NOT happening!). I add it to the Job Start of a 1 record do nothing job... Hopefully, you can tweak it to work for you. If you need help, let me know.

Sometimes COMP$ is CMP$ depending on what file you use as your base for the import job, just in case you run into a file not found on the first line.

@BarbaraOlson - I sincerely hope I don't have to use it, but WOW, COOL, in case I do! THANKS for sharing!

Sure, I actually took a few to generalize it a bit and make the import really general and foolproof... So I'm attaching a zip with a VI job, the perform logic and the dummy import file. Drop the PLACEHOLDERIMPORTDOC and ChangePDFDirectory.pl into a pl folder in the MAS90\VI folder. In ChangePDFDirectory.pl you would need to change your MAS 90 directory in the first line, then the Directory you need to redirect the PDFs to in the Let Directory line. You will manually move the PDFs in Windows Explorer, then redirect the path using this. You don't actually every have to run this job, just executing it triggers the Perform Logic, you can then cancel the job. Make sure you have a back-up first :D and of course, you can just replace PR with the AR PDF Log, etc to change these across all modules.

@BethBowers - About what number is the upper limit? Once upon a time, I determined that if you moved the paperless files via the WIN CUT command to the new folder, then used the move utility, the strain on MAS is negligible.

Two years in a row said they were moving 8001 records.

Last weekend I moved 43,000+ files, version 4.4. At the old server, I used the link utility to move to new server and it was not too bad, about 2 hours.

I had one recently with multiple companies and a separate folder for each module. So had to do LOTS of iterations, along with having to wait and wait for the screen to refresh after each run. Tedious.