Re: [DUG]: dbxoodbc

[Neven MacEwan]

Myles   Frustrations with ADO   I'm using Static/ClientSide/BatchOptimistic Datasets and the OLE DB Driver for SQL Server I suppose in ADO's defense I'm using a kbmMemTable in front of it and I have my own database Metadata system so I don't require a lot of its client side functions and metadata management but it is noisy (do a trace on what it requests)   ie it will request the format (metadata of a query) and then request the format of one column (the PK) within that query (duh!) and will do this for every little thing   It is hugely fat and as it is a COM object it has no compile time checking so you get untraceable runtime errors   I'm now facing updating a join query and I'm in fear of what it will do, the process is read docs, program, trace, try and guess why it does that then try and alter it, I feel like i'm modelling a large lump of clay with the sharp end of a needle   I think it would be fine if you were prepared do everthing the ado (read MSSQL as per MS Access) way but go outside their paradigms and it gets messy     Neven ----- Original Message ----- From: Myles Penlington To: Multiple recipients of list delphi Sent: Friday, September 27, 2002 11:17 AM Subject: RE: [DUG]: dbxoodbc Would you care to share your ADO frustrations ...? Myles.   -----Original Message----- From: Neven MacEwan [mailto:[EMAIL PROTECTED]] Sent: Friday, 27 September 2002 11:07 a.m. To: Multiple recipients of list delphi Subject: [DUG]: dbxoodbc Hi   After much ADO frustration I'm thinking of changing dbExpress and this open source ODBC driver, has anyone any experiance of dbxODBC   TIA    Regards Neven  N.K. MacEwan B.E. E&E  Ph 649 621 0001  Fax 649 621 0400  [EMAIL PROTECTED]