Sage 100

 View Only
Expand all | Collapse all

Moving Sage 100 2013 to 2016 and using the Library

Wayne Schulz

Wayne Schulz02-29-2016 12:41

Robert White

Robert White02-29-2016 12:48

Larry Bradford

Larry Bradford02-29-2016 12:50

Jim Woodhead

Jim Woodhead02-29-2016 16:46

Larry Bradford

Larry Bradford02-29-2016 16:58

Jim Woodhead

Jim Woodhead02-29-2016 17:34

Larry Bradford

Larry Bradford02-29-2016 17:42

  • 1.  Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 12:40
    Moving Sage 100 2013 to 2016 and using the Library Master - Link Maintenance Utility with 10s of thousands of records of paperless office documents to be moved to a new server. I have copied all over through windows but the utility is taking forever to load the screen and bring up the relink button and the hum of the servers is putting me to sleep. No VI so I can't import the new path into the current records (if that is even possible).


  • 2.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 12:41
    @JimWoodhead


  • 3.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 12:43
    Importing isn't possible. But Wayne is right - Jim helped me out a while back with a script he designed.


  • 4.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 12:44
    Sane thing has happened to me. In order to confirm everything is working...I decided to do it by company and module...there the volume was smaller and quicker


  • 5.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 12:47
    I have narrowed to a single company but even the one company has 24K records. It is taking for-ev-er.


  • 6.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 12:48
    Gotta love SQL for that reason alone!


  • 7.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 12:50
    But they love their PR and JC.


  • 8.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 12:50
    In our Evernote, LM, Upgrades, Paperless, look at PDFlogconvert


  • 9.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 13:19
    Not sure how many companies you have but I took the same approach as @LourdesSobrino and that worked for me. The largest module I had was 15K.


  • 10.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 13:23
    That's how I've been doing it, too. I can't stand the waiting.


  • 11.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 14:17
    @LarryBradford I need the old location and the new location. I can create a quick script for you.


  • 12.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 14:56
    I thought Jim had a solution that was posted in Evernote???? PATH CHANGE UTILITY Sage offers a way to change paths when you move paperless from one server to another. However that can be very slow for large quantities of documents. Below is an alternative which will do a search and replace on the server name/directory. Much faster. Be sure you make a backup of everything the instructions say will change. Installation 1. Copy or Save as the program, PDFLogConvertDirectoryV2, to the /MAS90/UTILITY subfolder. Note: The following tables in the /MAS90/MAS_SYSTEM folder will be changed (MAKE A BACKUP): * PL_JOURNALPDFLOG.M4T * PL_PERIODENDPDFLOG.M4T * PL_REPORTPDFLOG.M4T The follow tables with be changed for the current company (MAKE A BACKUP): * AR_CustomerPDFLog (if A/R is activated for the current company code) * AP_VendorPDFLog (if A/P is activated for the current company code) * PR_EmployeePDFLog (if P/R is activated for the current company code) Steps to run this program: 1. Make a backup of the above files. 2. At the MAS 90/200 Launcher menu, click on File/Run 3. Type in SYZCON and click OK. This will pop up a command mode screen 4. At the -> prompt, type RUN ""../UTILITY/PDFLogConvertDirectoryV2 and press <ENTER>.........


  • 13.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 16:29
    He is using the using the above technique. the issue is with a LOT of records the Sage Path change is slow. I can create a script to change the path instead of using the Sage Path Change utility. My script will take minutes.


  • 14.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 16:39
    I am going to log in and get the old and new path in just a minute.


  • 15.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 16:40
    I was using the Library Master - Utilities option


  • 16.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 16:46
    yeah my script is MUCH faster.


  • 17.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 16:48
    Well, they are currently using about 10 paths and I am consolidating to one path. I also cannot get my VPN connection and MSTSC to work.


  • 18.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 16:55
    I just need the part that changes. I will likely use a Find and replace logic. So if it is the same structure with a different server name just document it.,, or I can change it to one path. up to you.


  • 19.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 16:58
    All records.


  • 20.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 16:58
    It needs to change to \\masvirtual\sage\paperless office\


  • 21.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 17:34
    let me know how it goes.


  • 22.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 17:41
    I have time now to wait for that magical script that you might be offering...


  • 23.  RE: Moving Sage 100 2013 to 2016 and using the Library

    Posted 02-29-2016 17:42
    Never mind. I see Magic in my mailbox.