Lazarus, Zeos and Ms Access (mdb)

[Dali]

Mark, do you think there would be an easy way of connecting to an Access database via ODBC with Zeos components being Lazarus the compiler and Windows the target OS? Would such a thing require much work, other than simply commenting some conditional defines out like I did with ADO? Or would I need to write a whole driver from scratch? That might be a solution for me and, in fact, since OLEDB unit would not be required in that case, the patch could be committed, and I'd see it as a big step forward for the port of the whole Zeoslib to Lazarus.

[pingy]

I find myself in de same spot as Dali and wanted to give Lazarus/Zeos/ADO a try. Since this topic is running for more than 3 years, I wondered if there's any chance of ADO being incorporated into Zeos.
Besides that, the documentation states "For other databases we propose to use implemented Active Data Objects (ADO) Bridge". What is meant by this and, where is that bridge and where is it implemented? Does anyone have a clue to what I could do whith this statement?

[mdaems]

pingy,
As long as fpc/lazarus can't provide an oledb replacement and nobody writes his own odbc/ado driver for zeoslib this will not become available. There are 2 reasons for this:
- licence issue with oledb unit
- no volunteering developers to write a new zeoslib driver

Mark

[mdaems]

Correction! Apparently there's some odbcsql package in the fpc source code directory. No idea if it can be used to start a new driver, however.

Mark

[TheBlackSheep]

Don't know if anyone has looked into this recently - I have need to populate an MSAccess database (ideally via ADO) and although this is available in Delphi via Zeos it still isn't an option in Lazarus on Windows.

If the outstanding issue is an open source OleDB unit then there might be a possibility of using the open-source Synopse framework which has the SynOleDB unit.

[link=]http://synopse.info/fossil/wiki/Synopse+OpenSource[/link]

It seems to have some issues with compiling - the comments which are extensive have double/triple opening curly brackets which Delphi just ignores but FPC/Lazarus requires equivalent closed brackets and when it doesn't find any just treats all subsequent code as a comment - so that would need tidying.

There's a few dependencies to other files in the framework but might it be possible to modify it in such a way to make it work with Zeos?

TheBlackSheep

[EgonHugeist]

TheBlackSheep,

sounds great. Thoughts:

Somebody has to write them if we're allowed to provide/change theire codebase. If yes than we can start implement the SynOleDB. Don't hessitate to start theire. IF you would like to start than i propose to work with some defines like {$IFDEF ENABLE_SYNOLEDB}. The implementation should be available for FPC only i think.

Hint: OleDB becomes more and more deprecated. MSSQL2012 f.e. is the last Microsoft server who sopports the OleDB. All fututer relases usung the TDS-protocol or another library. I don't know what happens to MSAccess in this case.

[marcov]

The just released FPC 2.6.2 comes with TDS headers (and connection etc classes for SQLDB)

[EgonHugeist]

TheBlackSheep,

i wrote with the Synopse people. The use our ADO implementation. So this way is closed. I guess we need an ODBC-protocol like the FPC-SQLDB components do support...

[mdaems]

No way to reuse the fpc sqldb classes as they are in a new fpc-only zeoslib dbc driver? As far as I understand they are free to use.

Mark

[EgonHugeist]

Note:

Since 7.2 you can use the ADO-protocol for FPC too!