Sage 100

 View Only

  • 1.  Multiple Variable type and Variable file errors while upgrading from 4.05

    Posted 06-01-2020 18:25
    I'm trying to upgrade an old dinosaur 4.05 version, going through the rebuild keyed files and sorts process throughs up multiple variable file errors on the UDF tables. I've chosen not to rebuild these files, but did say yes to rebuild the IM_90xxx.soa file, just to see the impact. All 20,596 records were removed. I restored the original file which I had backed up. 

    I'm upgrading to an interim 4.50.8 before going to 2019. During the data conversion the IM conversion failed due to the 


    What would be the general consensus here? Will I need to setup imports to the 4.50.8 CI_Item for all those 20,596 UDFs and any other module files where the 4.05 UDFs should be migrated too?


    ------------------------------
    John Kerr
    Net at Work
    ------------------------------


  • 2.  RE: Multiple Variable type and Variable file errors while upgrading from 4.05

    Posted 06-02-2020 00:30
      |   view attached
    I don't recognize the last error and can't find anything in the KB for it.
    For the first error, that usually happens when providex tries to process a numeric value/variable with a function/method/directive intended for strings of vice versa.
    More than likely, you have a bad record with a bad value or key but in order to find it, you'll need to click Info and see what is displayed. If the info displayed is not enough to track it down, then you can use my program dump utility i attached from Info > Debug. Place the file somewhere easy to reference such as MAS90 or MAS90\CM\Script. From the debug/command window, type one of the lines below and press enter. The utility will output the file to MAS90\Home\Textout with session id info and timestamp info used in the file name.
    perform "<relative path to attached file>\dumpdata.pl" ​

! Example 1, in MAS90 directory on server.
perform "dumpdata.pl" ​

! Example 2, in MAS90\CM\Script directory on server.
perform "..\CM\Script\dumpdata.pl" ​
    Here's an example.

    If you attach the dumped data, i should be able to review it to locate the offending table and record.


    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------

    Attachment(s)

    pl
    DumpData.pl   278 B 1 version


  • 3.  RE: Multiple Variable type and Variable file errors while upgrading from 4.05

    Posted 06-02-2020 10:02
    Thanks very much David

    The second error is the prompt that appears while rebuilding the keyed file, simply indicating that an error in the file has been detected and asking if I want to go ahead with the rebuild. If I choose Yes, then all the UDF records are removed from the file. I couldn't find anything in the KB either.

    The other error occurs during data conversion. I will attempt to reconvert the data today and send you the dumped data.



    ------------------------------
    John Kerr
    Net at Work
    ------------------------------

    Original Message


  • 4.  RE: Multiple Variable type and Variable file errors while upgrading from 4.05

    Posted 06-02-2020 12:16
    John, looking in the IM_LEVELCONVERSION.PVC program, it looks like it's erroring out when converting the IM_ITEMVENDOR table.  Error 26 usually comes up when one of the fields is expecting a numeric value but encounters a string or maybe a bad date is out there as well.   If you do a DUMP of the variables you may be able to figure out what record is causing the issue.  You can try PRINT cSourceString$ when you get to the command prompt.

    ------------------------------
    Marcos DeLuna
    Deluna Consulting
    ------------------------------



  • 5.  RE: Multiple Variable type and Variable file errors while upgrading from 4.05

    Posted 06-02-2020 16:32
    If you can Debug, then:
    ? cSourceString$    (ENTER)
    It will show you either the problem record, or the record-before (last successful read) in the IM_12 file.

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

    Original Message


Related Content