Sage 100

 View Only

  • 1.  DATA CONVERSION 4.05 TO 4.50....to continue to 2019

    Posted 06-03-2020 20:50
    Doing test conversion from 4.05 to finish in 2019....the error is while converting teh data in 4.5 PU8
    I am getting Error #26 Variable Type Invalid Program PR_LevelConversion.pvc Line 1748
    Making reference in same file for multiple companies...not all of them

    The file is PRDxxx.SOA
    ​​

    ------------------------------
    Lourdes Sobrino
    LU² DSD Puerto Rico
    Guaynabo Puerto Rico
    787.485.9638
    ------------------------------


  • 2.  RE: DATA CONVERSION 4.05 TO 4.50....to continue to 2019

    Posted 06-04-2020 11:08
    What version is doing the conversion????? I checked 2017 and 2019 and line 1748 was a file Erase Stmt.

    Lee
    --

    Friendly Systems, Inc.

    Sage 100 (Mas90/200), Sage 300 (Accpac), SageCRM, xTupleERP
    Visit us on the web at www.friendlysystems.com
    Office:?? 678.273.4010 ext 4
    Mobile: 404.202.9065
    Fax:?????????? ??678.273.4012
    See our blog at www.friendlysystems.com/blog






  • 3.  RE: DATA CONVERSION 4.05 TO 4.50....to continue to 2019

    Posted 06-04-2020 11:43
    The error is when I do the conversion in v4.5 PU8...I wont let me go directly from 4.05 to 2019....

    ------------------------------
    Lourdes Sobrino
    LU² DSD Puerto Rico
    Guaynabo Puerto Rico
    787.485.9638
    ------------------------------

    Original Message


  • 4.  RE: DATA CONVERSION 4.05 TO 4.50....to continue to 2019

    Posted 06-04-2020 12:35
    Oops, I only have 4.5.7. which has the ERASE stmt at 1748

    Try the Debug Option then:
    ? cSourceString$   (ENTER)
    That should display the problem record.

    ------------------------------
    Lee Graham
    Friendly Systems, Inc.
    ------------------------------

    Original Message


  • 5.  RE: DATA CONVERSION 4.05 TO 4.50....to continue to 2019

    Posted 06-04-2020 12:49
    Lourdes, have you tried going to v2016 or v2017?  You don't need to stop at 4.5.8.  Data just has to be at 4.5.8 or higher before going to v2018.  If inventory is involved, maybe go 4.05 to 4.40 to 2017.

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 6.  RE: DATA CONVERSION 4.05 TO 4.50....to continue to 2019

    Posted 06-06-2020 09:05
    OK...Today I will try to install 2016 or 2017 and testing through that version first....I will let you guys no...thansk

    ------------------------------
    Lourdes Sobrino
    LU² DSD Puerto Rico
    Guaynabo Puerto Rico
    787.485.9638
    ------------------------------

    Original Message


  • 7.  RE: DATA CONVERSION 4.05 TO 4.50....to continue to 2019

    Posted 06-09-2020 22:16
    I installed v2017 and did the parallel migration...
    BUt then got the same error when converting the data in v2017


    ---------------------------------
    Lourdes Sobrino
    LU² DSD Puerto Rico
    Guaynabo Puerto Rico
    787.485.9638
    ---------------------------------



    Original Message


  • 8.  RE: DATA CONVERSION 4.05 TO 4.50....to continue to 2019

    Posted 06-10-2020 02:48
    Edited by Alnoor Cassim 06-10-2020 02:49

    What is the Line Number now? What Lee said above is still relevant where you click on Info then Debug and at prompt type:

    PRINT cSourceString$ 

    You could also type this variation and paste (Ctrl-V) into Notepad or Word

    CLIP_BOARD WRITE cSourceString

    If we are in the PRD conversion block, the 1st 3 characters of cSourceString$ will be the key in PRDxxx.SOA to the bad record you can select with DFDM. It sounds like one of the numeric fields is incorrectly stored as string data so you would have to fix that field to be numeric again. 



    ------------------------------
    Alnoor Cassim

    Accounting Systems, Inc. (ASI)
    Email: alnoor@asifocus.com
    Orange County, CA
    ------------------------------

    Original Message


  • 9.  RE: DATA CONVERSION 4.05 TO 4.50....to continue to 2019

    Posted 06-10-2020 09:49
    Did you do a Rebuild Key files on the 4.5 version first?
    Possible to check the record being updated that causes the err-26 via the debug steps?
    Or scroll through the Earnings and Deduction codes to look for odd records?

    ------------------------------
    Lee Graham
    Friendly Systems, Inc.
    ------------------------------

    Original Message


Related Content