Skip site navigation (1) Skip section navigation (2)

Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Ludek Finstrle" <luf(at)pzkagis(dot)cz>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error
Date: 2005-12-16 16:34:53
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7EAA8@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
 

> -----Original Message-----
> From: Ludek Finstrle [mailto:luf(at)pzkagis(dot)cz] 
> Sent: 16 December 2005 16:00
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)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.

Responses

pgsql-odbc by date

Next:From: Ludek FinstrleDate: 2005-12-16 17:06:52
Subject: Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error
Previous:From: Dave PageDate: 2005-12-16 16:32:38
Subject: Re: Does postgresql-odbc work on 64-bit platforms?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group