Lookup fails with Sage 50 database connector (9 replies)
Steve, have you fully patched the Sage50 software?
Yes as far as I know. It updates itself to SP 5 and a check for updates says it is up to date.
Steve, there's an SP7 (which doesn't come down through the auto-updates...ask Sage).
Can you please install this and let me know.
Thanks
This didn't help unfortunately. Could it be anything I'm doing wrong?
(Incidentally the SP7 install was very odd. There was an update for S21DBC32.dll but it tried and failed to install to Windows\System32 on a 64 bit system. Had to copy that file manually to Windows\SysWOW64)
Any more thoughts on this? We have a stalled project that depends on the lookup (or an alternative). Thanks.
Steve, I will move this into our support system.
Did this get resolved Steve?
Yes it was resolved, John. It's a fault in Sage 50 rather than IMan and Sage are not cooperative on it.
Instead those fabulous people at Realisable added a function in IMan v3 update 3 as follows:
"Sage50 Connector – Added Sage50 lookup function to provide direct API access for translation and lookups against the Sage50 database. This function provides the ability to lookup against the Sage50 and to bypass the ODBC lookups using the Sage50 ODBC driver, which occasionally fails"
Closed due to inactivity.
Hello,
I have a LOOKUP set up that uses a Sage 50 database connector. The connector seems to work fine and can be used happily with DB reads.
The lookup returns intermittent results with an error on each 'partial results' refresh as follows:
Error whilst evaluating field [Sage_Account_Ref] on transaction type [WebOrder].
Resolved Function - Lookup( "S50Customer", "ACCOUNT_REF", "[email protected]", False )
Error - Description: Data provider or other service returned an E_FAIL status.
The failed parameter value tends to be a different one each time, so it's not always failing on the same 'wherevalue'. Further the field using the lookup gets populated differently each time. Different records have a returned value each time a refresh is invoked.
I have tried rewriting the integration and it's the same every time. Also fails with the same message when run as a schedule.