|From:||"Markus Donath" <md-postgres-donath(at)netapps(dot)de>|
|Subject:||Re: odbc driver problem? or threading? or crecordset?|
|Views:||Raw Message | Whole Thread | Download mbox|
did you try the latest build ?
""Vincent Ladlad"" <vincentl(at)ntsp(dot)nec(dot)co(dot)jp> schrieb im Newsbeitrag
> 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
> 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?
> 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
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
|Next Message||Stergios Zissakis||2004-03-16 10:27:24||Re: Mutli-threading and performance of ODBC|
|Previous Message||Vincent Ladlad||2004-03-16 01:23:35||odbc driver problem? or threading? or crecordset?|