Alan Holden wrote:
That error message (if it's actually coming from the JDBC driver and not BD) leads me to think that the DSN is actually working, just a little bit.
I'm pretty sure that error is coming from the driver. If verifying a datasource fails in the admin I just spit out the error message from the driver, and given the fact that he seems to be getting the same error even after the datasource is manually configured, chances are that's where it's coming from.
Also on "other" type datasources, you really need to provide a verification query for them to be verified correctly through the admin interface--what query are you using? Typically you'd just use something appropriate to the database type in question, like running a now() type function you know will work correctly.
-- Matt Woodward [email protected] http://www.mattwoodward.com/blog Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html
smime.p7s
Description: S/MIME Cryptographic Signature
