odbc driver problem? or threading? or crecordset? - Mailing list pgsql-odbc

From Vincent Ladlad
Subject odbc driver problem? or threading? or crecordset?
Date
Msg-id 014701c40af5$4d6c6070$643b1cac@Titanium
Whole thread Raw
List pgsql-odbc
hi there!   im new to psqlodbc, and i hope you pros could help me out :)

i have been browsing the internet for more than
a week now, searching for clues regarding an
"access violation" error.  i hope maybe you can
help me get over this problem, as it has been
eating my dev schedule.

here's the problem:
i have two threads triggered by onTimer which
is set to 1 second.  when the timer expires,
the threads are notified, and a (select) query is started.
both threads use the same recordset class, but
different instance.  thread1 accesses server1 using datasource1. thread2
accesses server2 using datasource2. both tables are the same on both
servers, but have different values. that is why they  use the same
recordset.
after a few timerEvents, the program stops, and the
error message "access violation" is shown.
during debug, i traced that the error occurs when
both thread attempts to call the crecordset::open function.
at the same time.  even though they access different
datasources, the problem keeps coming back.  i only
issue a simple select statement with the following options --
(crecordset::snapshot, crecordset::readonly).

the recordset is open()ed and close()d after every query.
the cdatabase instance is not. it remains open.

is there something i missed?

thanks,
vincentl

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.605 / Virus Database: 385 - Release Date: 3/1/2004



pgsql-odbc by date:

Previous
From: Steve Jorgensen
Date:
Subject: Some problems with Access and ODBC to PostgreSQL
Next
From: "Markus Donath"
Date:
Subject: Re: odbc driver problem? or threading? or crecordset?