[DB-SIG] mxODBC: Function sequence error

Thomas Waechter waechter at cenix-bioscience.com
Mon May 24 09:55:12 EDT 2004

Hornberger, Chris wrote:
> What about, rather than handing out cursors to threads, you 
 > sacked/queued your requests, and have a centralized db
> manager? That way you only have to lock the queue object 
> during pop/push actions, and part of the "job" object you stack up
> can have a call back thru' which you return the results.

I am working with a general database adapter which only gets specialized 
for the different data sources. Mostly we are using Postgres, but now I 
trying to write a specialization for ODBC 2.0 compliant data sources to 
access a Filemaker database using mxODBC. I am using Access only as my 
testing platform, because it is better supported.

Therefore I don't want to have a central manager, because the database 
driver in the lower level will call the database for me. Psycopg is 
doing this for Postgres and mxODBC is doing this work for ODBC data sources.

Because there occurred errors due to concurrent read access I emulated 
the stack in making all calls to mxODBC mutual exclusive. For mxODBC now 
  all calls are coming in sequence, in the same way, as there would be a 
central manager. Unfortunately I still get the same "function sequence 
error" from the MS Windows ODBC manager for my Access ODBC Driver.

Thomas Waechter
Software Developer
Cenix BioScience
BioInnovations Zentrum
Tatzberg 46

Tel : +49 (0)351 4173 0155
e-mail : waechter at cenix-bioscience.com
Cenix Website : http://www.cenix-bioscience.com

More information about the DB-SIG mailing list