[python-win32] Adding a really odd feature to Access as an odbc driver

[Tim Roberts]

Grzegorz Adam Hankiewicz wrote:
>
> I have an old application which uses Access, and possibly the reason
> why concurrent access wasn't designed is because transactions are not
> supported, so multiple writes could be trouble.

Access is trouble any time you have more than about 2 people using a
single database.  It just wasn't designed for that environment.


> I was wondering if it would be possible to serialise all the
> read/write operations through a micro server with pywin32+twisted. I
> guess this is possible since the server just reads requests and deals
> them in a syncronous way. However, would it be possible to connect
> from the application to this serialisation server through odbc? Would
> this mean implementing a dummy odbc driver which just relays/gets the
> information and install it in the client?

Surely it would be MUCH less trouble to move the backend to Postgres,
SQLite, or even SQL Server Express, all of which are free.


> The idea is implementing this behind the scenes without requiring to
> touch the original application. Is this possible at all?

Is the original application in Access?  Or is it another language that
just happens to use the Jet database?  What API does it use to talk to
the database?

-- 
Tim Roberts, timr at probo.com
Providenza & Boekelheide, Inc.