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

PgODBC + Borland C++ Builder problems

From: "Geoffrey C(dot) Speicher" <geoff(at)sirius(dot)trassociates(dot)com>
To: pgsql-interfaces(at)postgreSQL(dot)org
Subject: PgODBC + Borland C++ Builder problems
Date: 1999-05-16 21:12:41
Message-ID: Pine.BSF.4.05.9905161642570.50311-100000@sirius.speicher.org (view raw or flat)
Thread:
Lists: pgsql-interfaces
I have been using BC++ Builder for a few weeks now to build an interface
to a PostgreSQL database via the pgODBC Win32 driver, and there seems to
be some incompatibility between the two.

Particularly, BCB and programs created with it will frequently result in
an access violation in KERNEL32.DLL.  The BCB user community does not
report such behavior with other ODBC drivers, but there was mention of
something similar with an older "buggy" driver for MS-SQL or something
along those lines.

Example:

  1. Open data source + table in BCB-built program
  2. Open dialog containing a form and data controls for the data source
  3. Immediately jump to last record in table
  4. Witness program crash (access violation in kernel32.dll)
     [This happens after a pause of a few seconds, during which the
      program displays the "waiting for SQL" mouse pointer.]

However, if between steps 2 and 3 you browse though the records in the
table, then jumping to the end does not crash the program.  Further, there
are some tables for which the crash never happens, but I cannot find any
pattern for determining whether or not a particular table will cause it.

The problem also affects actions such as filling a combo box with the
contents of a table.  Again, for some tables, the combo box will fill just
fine, and for others it will crash.

Any ideas?

Geoff


Responses

pgsql-interfaces by date

Next:From: Peter HarveyDate: 1999-05-17 01:35:43
Subject: Re: [INTERFACES] ODBC
Previous:From: selkovjrDate: 1999-05-16 19:24:24
Subject: Re: [GENERAL] Trying to make functions in 'C'

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