Re: ODBC - Getting CONN ERROR: errmsg='The buffer was too small for the InfoValue'

2018-07-13 Thread Edgard Battisti Guimarães
Ok, Done! thanks for you help Em sex, 13 de jul de 2018 às 10:29, Adrian Klaver escreveu: > On 07/12/2018 04:56 PM, Edgard Battisti Guimarães wrote: > > --- The ODBC Global tracing was turned on too but any one entry was made > > from the powerbuilder app. > > > > --- No problem on sending the

Re: ODBC - Getting CONN ERROR: errmsg='The buffer was too small for the InfoValue'

2018-07-13 Thread Adrian Klaver
On 07/12/2018 04:56 PM, Edgard Battisti Guimarães wrote: --- The ODBC Global tracing was turned on too but any one entry was made from the powerbuilder app. --- No problem on sending the entire PB app, but it's really big, so follows the initial script with the connect and the ini file content

Re: ODBC - Getting CONN ERROR: errmsg='The buffer was too small for the InfoValue'

2018-07-12 Thread Edgard Battisti Guimarães
--- The ODBC Global tracing was turned on too but any one entry was made from the powerbuilder app. --- No problem on sending the entire PB app, but it's really big, so follows the initial script with the connect and the ini file content with the parameters. I will make a minimalist PB script to

Re: ODBC - Getting CONN ERROR: errmsg='The buffer was too small for the InfoValue'

2018-07-12 Thread Adrian Klaver
On 07/12/2018 05:19 AM, Igor Korot wrote: ,Hi, On Wed, Jul 11, 2018 at 10:33 PM, Edgard Battisti Guimarães wrote: I've ported a powerbuilder application to postgresql. Tested ok on windows 10 64, was installed on two win10-64 other computers, all connecting the postgresql database in the loca

Re: ODBC - Getting CONN ERROR: errmsg='The buffer was too small for the InfoValue'

2018-07-12 Thread Igor Korot
,Hi, On Wed, Jul 11, 2018 at 10:33 PM, Edgard Battisti Guimarães wrote: > I've ported a powerbuilder application to postgresql. Tested ok on windows > 10 64, was installed on two win10-64 other computers, all connecting the > postgresql database in the localhost with access via odbc. The third o