Sage 100

 View Only
  • 1.  Has anyone run into this error with trying to acce

    Posted 06-13-2017 07:42
      |   view attached
    Has anyone run into this error with trying to access Sage via MS Access using ODBC? ODBC Call Failed [ProvideX][ODBC Driver][FILEIO] Unable to allocate memory to perform requested operation (#14)


  • 2.  RE: Has anyone run into this error with trying to acce

    Posted 06-13-2017 07:49
    Is this an established DB that you are just updating? CS ODBC in play? Not fond of these messages as they are too cryptic. PTQ or a linked table? Verify the path to Sage?


  • 3.  RE: Has anyone run into this error with trying to acce

    Posted 06-13-2017 07:52
    The customer is rolling their own so unfortunately, I'm the recipient of the ""why is Providex ODBC so bad"" type question. I haven't been retained to develop or maintain their queries so unsure that further debug is within the scope of support. Generally, once I can connect via Crystal Reports and pull data I consider the connection WAD and suggest that the customer places a call to Sage.


  • 4.  RE: Has anyone run into this error with trying to acce

    Posted 06-13-2017 08:20
    I think it means the returning resultset is too large for the ODBC driver.


  • 5.  RE: Has anyone run into this error with trying to acce

    Posted 06-13-2017 09:12
    I'm with @SteveIwanowski on this. Sometimes if I log out of the database, go back in, refresh the links using Link Server Manager, I can get by. Sometimes not. I usually avoid querying large files choosing to build tables from selected records then querying from that. In any event, this is probably beyond your support agreement.


  • 6.  RE: Has anyone run into this error with trying to acce

    Posted 06-15-2017 11:39
    Followup: Called Sage and attempted to open a case but they don't want to know. Refused to open case since tech was positive Sage would not research it or support the query.


  • 7.  RE: Has anyone run into this error with trying to acce

    Posted 06-15-2017 11:45
    What?!? Wow, that's, uh, honest...