Create an ODBC Driver

[marabu]

Hi mohfa,

neither ODBCInst nor ODBCConst seem to be proper names for Units that contain your BDE replacement components. Judging by name both Units could be part of your ODBC driver implementation. You could base your architectural decisions on a close study of the Units DB and DBTables. One thing is for sure: There should not be much dependency between your components and your driver.

Regards

[mohfa]

Zitat von marabu:

Hi mohfa,

neither ODBCInst nor ODBCConst seem to be proper names for Units that contain your BDE replacement components. Judging by name both Units could be part of your ODBC driver implementation. You could base your architectural decisions on a close study of the Units DB and DBTables. One thing is for sure: There should not be much dependency between your components and your driver.

Regards

OK as for you what is the appropriate place to decalre my Dataset or i should not declare it but use DBTABLES and DB unites .

[marabu]

As I understand the given (Borland) architecture you will have your own components (TMohfaDataSet e.a.) in a Unit named MOHFADB - to distinguish it from ADODB and others. Your TMohfaDataset should be derived from TCustomMohfaDataSet which in turn should inherit directly from TDataSet. Your task is to implement the abstract methods from TDataSet in your own class TCustomMohfaDataset and to publish a compatible (see TADODataset) set of properties in your class TMohfaDataset. Please make good use of the sources that came with your Delphi Enterprise Edition and make sure you read the relevant chapters in the documentation.

Regards

[Reinhard Kern]

Zitat von marabu:

As I understand the given (Borland) architecture you will have your own components (TMohfaDataSet e.a.) in a Unit named MOHFADB - to distinguish it from ADODB and others. Your TMohfaDataset should be derived from TCustomMohfaDataSet which in turn should inherit directly from TDataSet. Your task is to implement the abstract methods from TDataSet in your own class TCustomMohfaDataset and to publish a compatible (see TADODataset) set of properties in your class TMohfaDataset. Please make good use of the sources that came with your Delphi Enterprise Edition and make sure you read the relevant chapters in the documentation.

Regards

Hello marabu, are you sure that creating a custom TDataSet results in a generally usable ODBC-driver? I think this was the original question.

SY Reinhard

[marabu]

Hi Reinhard,

it wasn't me who started to write about TDataSet in the first place, but I think it is necessary anyway. I most certainly never did suggest to write a TDataSet-Successor in order to implement an ODBC-Driver.

The original poster has informed us about his own implementation of an SQL-92 based (local) RDBMS by means of TTable, TQuery, TDatabase. Just to recap: He is looking for a way to present an ODBC driver to his client, so that other tools cann access the data, too.

My suggestion to Mohfa is to start reading all the readily available documentation to learn about the architecture, so his components fit in nicely. At this moment he seems to mix up the two concepts (data-aware component vs. ODBC driver) badly. Even when local data access is implemented directly by his components, he will never succeed with his ODBC driver by trying to repackage his components. The first task should be to sort out the functionality that comprises a solid call level interface to his RDBMS. The CLI can then serve as the basis for the ODBC driver - and for the components as well.

Regards

[mohfa]

Hi marabu

Zitat von marabu:

At this moment he seems to mix up the two concepts (data-aware component vs. ODBC driver) badly. Even when local data access is implemented directly by his components, he will never succeed with his ODBC driver by trying to repackage his components. The first task should be to sort out the functionality that comprises a solid call level interface to his RDBMS. The CLI can then serve as the basis for the ODBC driver - and for the components as well.

first i'm not trying to repackage my components , cause every thing goes well with the components and even the output File(s) all what i'm trying to do is to implement my Main RDMS unit to the ODBC Driver and i think that's what should i do otherwise how this ODBC Driver will recognise is it working with my RDBMS and not an other RDBMS and because the ODBC Driver is based only on the SQL functions .

regards.