Sage 100

 View Only
  • 1.  Customer getting Database Connector Error: [Databa

    Posted 05-19-2017 13:41
    Customer getting Database Connector Error: [Database Vendor Code: 9] when trying to print the Backorder Fill Report upon PO Receipt of Goods. I have checked the receipt files, the PO files AND open SO files. While I found a few missing dates, I have entered them and the error persists. Any ideas?? v2016 Standard 5.30.2 \ They do have ACS's WOEP enhancement.


  • 2.  RE: Customer getting Database Connector Error: [Databa

    Posted 05-19-2017 13:45
    Pretty sure this is a 'bad' date record error, not just a missing date. You need to look at all the date fields to make sure they are formatted properly.


  • 3.  RE: Customer getting Database Connector Error: [Databa

    Posted 05-19-2017 13:46
    Sorry, I did that as well.


  • 4.  RE: Customer getting Database Connector Error: [Databa

    Posted 05-19-2017 13:47
    If you change the odbc sotamas90 to allow null dates i think the report should run and you can scour it for the bad date.


  • 5.  RE: Customer getting Database Connector Error: [Databa

    Posted 05-19-2017 13:51
    Good thought @NancyHanson but the error persists.


  • 6.  RE: Customer getting Database Connector Error: [Databa

    Posted 05-19-2017 13:54
    My question is, what files is this report looking at (besides PO files)? I've looked at backordered SO's and they all have valid dates as well. I'm missing something....


  • 7.  RE: Customer getting Database Connector Error: [Databa

    Posted 05-19-2017 13:58
    A couple things to do.... Look at the report in Crystal to see the files used and review those tables. If it is a WRK table.. DO a preview and copy the WRK to the TEMPLATE WRK table and run the report Outside of SAGE directly in Crystal.. Also you can look at WRK table with DFDM


  • 8.  RE: Customer getting Database Connector Error: [Databa

    Posted 05-19-2017 14:32
      |   view attached
    OMG, I totally forgot about WO!! There were two WO's with no required dates for the components. Once I scheduled them, all is well. Thanks @JimWoodhead - it was opening the report and running in Crystal (even with no data) that had the WO heading that pointed me in the right direction.


  • 9.  RE: Customer getting Database Connector Error: [Databa

    Posted 05-20-2017 08:14
    Similar situation hit me on Thursday, client using Crystal SO header/detail report developed ages ago. Was populating any data. Traced it back to missing data in fields. Need to go back to UDF and make the field entry mandatory.