Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error - Mailing list pgsql-odbc

From Dave Page
Subject Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7EAA8@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Access violation C5 error on Visual FoxPro SQLEXEC() call after error  ("Andrus Moor" <eetasoft@online.ee>)
Responses Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error
List pgsql-odbc

> -----Original Message-----
> From: Ludek Finstrle [mailto:luf@pzkagis.cz]
> Sent: 16 December 2005 16:00
> To: Dave Page
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Access violation C5 error on Visual
> FoxPro SQLEXEC() call after error
>
> > We need to be reducing the number of options, not
> increasing them if at
> > all possible!
>
> I don't agree as administrator :-) It's better for users to just click
> some options instead of studying special commands.

I think you misunderstand - I want to avoid having any options/commands.
Zero configuration if possible.

Regards, Dave.

pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Does postgresql-odbc work on 64-bit platforms?
Next
From: Ludek Finstrle
Date:
Subject: Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error