It has to be a driver if it's true that the code is exactly the same. It's the only thing standing between OpenBD and the database. And only a driver issue would let the code run without throwing an error. Right?
On Mon, Apr 25, 2011 at 6:28 PM, Matthew Woodward <[email protected]> wrote: > On Mon, Apr 25, 2011 at 4:27 PM, Matthew Woodward <[email protected]> > wrote: >> >> Actually OpenBD does ship with the MS driver but you should certainly try >> swapping the driver if you're using the jTDS driver. > > To clarify, OpenBD ships with both the MS *and* the jTDS drivers. Would be > worth checking driver versions also to make sure the one you're using > outside the context of OpenBD matches the one you're using in OpenBD. > > -- > Matthew Woodward > [email protected] > http://blog.mattwoodward.com > identi.ca / Twitter: @mpwoodward > > Please do not send me proprietary file formats such as Word, PowerPoint, > etc. as attachments. > http://www.gnu.org/philosophy/no-word-attachments.html > > -- > official tag/function reference: http://openbd.org/manual/ > mailing list - http://groups.google.com/group/openbd?hl=en > -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
