pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
ODBC Problems
2+ messages / 2 participants
[nested] [flat]

* ODBC Problems
@ 1998-11-02 16:57 Vera Sabina Gelerenter <sabina@mecon.ar>
  0 siblings, 0 replies; 2+ messages in thread

From: Vera Sabina Gelerenter @ 1998-11-02 16:57 UTC (permalink / raw)
  To: pgsql-interfaces

I have installed the postgresql driver in a NT 4.0 Server with Internet
Information Server 4.0. I use it in a group of ASP pages and they run
OK.
When I try to run the same ASP pages in another NT 4.0 Server but with
Internet Information Server 3.0 I have the following error:

error 'ASP 0115' 
Unexpected error 
/bboard/AspDocs/conectar.asp 
A trappable error occurred in an external object. The script cannot
continue running. 

I think the problem is about the interaction between the postgresql
driver and
the ASP pages, because I can use the postgresql driver with another
aplications
in the same server that I get the ASP errors.

The postgresql driver version is 6.30.0250
The ODBC driver version is 3.0.28.22

I attach the psqlodbc.log file. The sql.log file is empty.

It's really necesary for us to resolve this problem as soon as posible.
Sorry for my english and thank you for your time.


 
Vera Sabina Gelerenter
Analista de Sistemas
Ministerio de Economia
Proyecto Informatica 
tel 349-8868/8041

Attachments:

  psqlodbc.log (application/x-unknown-content-type-fma004, 6.6K) download

^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* ODBC Problems
@ 2002-07-17 09:45 Stavros Karposilos <apcl79@dsl.pipex.com>
  0 siblings, 0 replies; 2+ messages in thread

From: Stavros Karposilos @ 2002-07-17 09:45 UTC (permalink / raw)
  To: pgsql-interfaces

    I am using psqlODBC v7.2.1 to connect a Redhat 7.2 Server running PostgreSQL v7.1.3 to a Win2K client running MS Access 2K.
    I have created an application which works fine for some time, but after that I get error messages which prevent me from opening and closing forms.
    Once, I got the message "Could not send query to the backend" right before the same situation with the forms started.
    I suspect that the driver closes the connection to the backend without informing the frontend, making the second do all weird things.
    I have tried some workarounds. I used a timer to refresh the table links every 1 min, but the command --CurrentDB.TableDefs("ItemsMain").Fields.Refresh-- didn't help on solving the problem and the command --CurrentDB.TableDefs("ItemsMain").RefreshLink-- seems to work, but every time it is executed it adds 350Kbytes to the Frontend Database file. After 10min the file has become 3MB, which are empty.
    Is it possible to change some settings on the driver so that the connection never closes, or to automatically reestablish the connection to the backend when closed?

    This small detail is the difference between a fully working program and a useless bunch of code. I would really appreciate any help.
    If this behaviour cannot change, do you have any recommendation on using another GUI frontend capable of running on Windows Boxes featuring tighter integration with PostgreSQL?

  Thank you in advance,
  Stavros Karposilos

^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2002-07-17 09:45 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-11-02 16:57 ODBC Problems Vera Sabina Gelerenter <sabina@mecon.ar>
2002-07-17 09:45 ODBC Problems Stavros Karposilos <apcl79@dsl.pipex.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox