Sage 100

 View Only
  • 1.  Strange character ascii(126), hex(E1) is screwing up record key in IM_ItemCost flie

    Posted 03-15-2024 14:36
    Dear List,

    ???????? Back in January, customer created/imported a Receipt of Goods and the Item_Cost records got screwed up for a receipt.
    The Group-Code in the record has two ascii(126), hex(E1) characters added at the end of the numeric data.

    People cannot select this record.
    Seen this before?
    How to correct in Sage DFDM?

    Thanks,

    Lee Graham
    --

    Friendly Systems, Inc.

    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


    Virus-free.www.avg.com


  • 2.  RE: Strange character ascii(126), hex(E1) is screwing up record key in IM_ItemCost flie

    Posted 03-15-2024 15:10
      |   view attached
    See screen attached.
    --

    Friendly Systems, Inc.

    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


    Virus-free.www.avg.com





  • 3.  RE: Strange character ascii(126), hex(E1) is screwing up record key in IM_ItemCost flie

    Posted 03-15-2024 15:12

    Lee,

    It looks like you are using DFDM on an older version of Sage 100. On the newer versions you can actually see control characters like that in the edit screen and they are easier to get rid of.

     

    You can still change that in DFDM in the older versions, you might need to backspace out one or two characters and make a change to that field click on "OK" and answer YES when prompted with "Remove Old Key"  then change the data back to what it should be without the special characters and again click on "OK" answer YES when prompted with "Remove Old Key" that should effectively remove those extra characters, which by the way were probably copy/pasted from a document that included a carriage return or something similar.

     

     

     

     

     

     

    Don't miss out on the 2024 Basic Crystal Reports for Sage 100 Online Training: View the details

     

    Don't miss out on the 2024 Intermediate Crystal Reports for Sage 100 Online Training: View the details

     

     

     

    David Overholt

    DWD Technology Group, Inc.

    9921 Dupont Circle Drive West, Suite 300 | Fort Wayne, IN 46825

    260.423.2414 main

    260.399.8655 Direct

    800.232.8913 toll free

    sagesupport@dwdtechgroup.com

    www.dwdtechgroup.com

     

    A black background with white text  Description automatically generated

     






  • 4.  RE: Strange character ascii(126), hex(E1) is screwing up record key in IM_ItemCost flie

    Posted 03-15-2024 15:33
      |   view attached

    What I found was that if I type over the old data and pad out with spaces, it works.  However, before coming to that I had just clicked in at the end of the existing data and types several spaces, and ended up with a mess - see attached.  Any ideas on recovering these records?



    ------------------------------
    Phil McIntosh
    Friendly Systems, Inc.
    ------------------------------



  • 5.  RE: Strange character ascii(126), hex(E1) is screwing up record key in IM_ItemCost flie

    Posted 03-18-2024 09:18

    Phil, 

    look at field #1 and the Key that is displayed above it; those two should always be the exactly the same. I would make a backup of that and also copy a test company. Then in that test company, try changing field #1 to match what is in the key field. I don't think I have ever seen the exact error message before, but you should be able to make that change still by clicking on the edit button. .



    ------------------------------
    David Overholt
    DWD Technology Group
    ------------------------------



  • 6.  RE: Strange character ascii(126), hex(E1) is screwing up record key in IM_ItemCost flie

    Posted 03-18-2024 09:22

    Thanks @David Overholt

    What I ended up doing was creating a couple of extra records by saying NO to the delete old key? prompt, editing them, and deleting the garbled records.



    ------------------------------
    Phil McIntosh
    Friendly Systems, Inc.
    ------------------------------