Sage 100

 View Only
  • 1.  Recently upgraded a client from version 4.20 to 4.

    Posted 09-19-2012 08:56
    Recently upgraded a client from version 4.20 to 4.50.pu4. Now receiveing Error 41 in AP Period End Processing due to invalid integer in several of the 2,877 records in the AP_Vendor1099Payments.M4T table. At the Error message clicked Info and then Debug to get to the > prompt. What are the commands in BF to display the following fields: APVendorNo,FormType1099,CalendarYr,BoxID,BoxText,BoxAmt. Thanks


  • 2.  RE: Recently upgraded a client from version 4.20 to 4.

    Posted 09-19-2012 09:24
    I had the same error in the same process last week but in a different table. the 0 (zero) was missing in one date field.Whereas all the other records had 09,for Sept, one record had just a 9


  • 3.  RE: Recently upgraded a client from version 4.20 to 4.

    Posted 09-19-2012 09:55
    This happened quite frequently at one particular client last spring. I exported via VI to a CSV (Excel Query was useless). Opened in notepad and searched. Found it fairly easily.


  • 4.  RE: Recently upgraded a client from version 4.20 to 4.

    Posted 09-19-2012 10:02
    @haroldwestover I used DFDM to look at the offending record based on the error message. I also looked at records before and after the offending record and could not spot the field with an ""INVALID INTEGER"" all fields looked ok in DFDM. I'm hoping by using DEBUG I can pinpoint the BAD field. I'm guessing there are about 25 records with an ""INVALID INTEGER"" field out of 2,877 records in the table.


  • 5.  RE: Recently upgraded a client from version 4.20 to 4.

    Posted 09-19-2012 11:04
    John Beyer with Realized Solutions shared this utility on LinkedIn. Maybe this will find the problem records for you. John provided the utility at no charge and said it was OK to share.

    Attachment(s)

    zip
    MAS90_DateValidator.zip   597 KB 1 version
    msi
    MAS90DateValidatorSetup.msi   804 KB 1 version


  • 6.  RE: Recently upgraded a client from version 4.20 to 4.

    Posted 09-19-2012 11:32
    @JaneCavanaugh Thank you for this cool utility. I ran it against my test data (Copied from orginal company data) and the original data and the utility reported that all dates in 778 tables in each company are GOOD! Can someone tell me if the DEBUG syntex is something like this: >?APVendorNo$ >?FormType$ , >?BoxAmt.


  • 7.  RE: Recently upgraded a client from version 4.20 to 4.

    Posted 09-19-2012 12:11
    From an old post somewhere: Another way is to check ""NULL Date"" in the SOTAMAS90 DSN, then run rpt in Crystal. Now error won't appear, rpt will complete and you'll see the bad dates appear (as a string). Now sort report by the date field. Most bad date values will appear at the top now (or at bottom). Once fixed in MAS, sort by other date fields in the table in case there are bad ones in there.