What's the statement?
I changed the Provider in the connection string from SQLNCLI11 to SQLNCLI10, and now it works.
John, be very careful of using the 10 driver.
The 10 driver has a known lockup issue with Sage300 and anything which opens/closes database connections; the 11 driver does not.
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
We have a DBReader with a query that fails. The error I see when I try to open the DBReader in the designer is :
"Deferred prepare could not be completed.
Statement(s) could not be prepared.
Invalid object name ..."
In Auditlog, I only see the "Invalid object name..." part of the message.
The query executes when I run it directly in SSMS, using the same login/password as is in the connection string in IMan.
Do you have any suggestions to help us get around this error?