As the same ODBC driver (Windows 10 SQL Server) works w/o a problem when using a user or system DSN connection, the driver should not be the problem.
Regards, Matthias Rebbe free tools for Livecoders: https://instamaker.dermattes.de https://winsignhelper.dermattes.de > Am 26.10.2018 um 00:21 schrieb Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com>: > > Re: [resolved] Microsoft - Driver Manager ODBC - Invalid string or buffer > length > > > > Hi, > Are you using 64 bit sql server 2014? Please take a look at an article > about:http://stackoverflow.com/questions/26745417/invalid-string-or-buffer-length. > Best regards > Sabrina > -- > Don't forget to give kudos when a reply is helpful and click Accept the > solution when you think you're good with it. > > > >> On Oct 25, 2018, at 15:04 , Matthias Rebbe via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> Thanks Mark, >> >> isn´t the DBQ parameter used when you want to access a file based Database >> like Access .mdb files? >> >> I tried it anyway, but added a "e before tAccessDBFilename, as it seems >> that was missing in your example. >> Still getting the buffer error >> >> [Microsoft][ODBC Driver Manager] Ungültige Zeichenfolgen- oder Pufferlänge >> In English something like this: Invalid string or buffer length >> >> >> Regards, >> >> Matthias > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
