Using ODBC through BDE - opinions wanted

Using ODBC through BDE - opinions wanted

Post by Brett Alcor » Sat, 20 Jul 1996 04:00:00



Fellow Delphi programmers,

  Just a quick question. I want to use a FoxPro-style database (DBF
files with CDX indexes) from Delphi. I haven't been able to find a BDE
driver but there is a standard Windows 95 FoxPro ODBC driver.

  I'm after opinions: is it worth pursuing the option of using ODBC
through the BDE? I have heard it is slow and my preliminary attempts
have shown the setup to be quite cumbersome.

Thanx
Brett

 
 
 

Using ODBC through BDE - opinions wanted

Post by Alan Pop » Sun, 21 Jul 1996 04:00:00


On Fri, 19 Jul 1996 20:04:50 +1100, Brett Alcorn


>  Just a quick question. I want to use a FoxPro-style database (DBF
>files with CDX indexes) from Delphi. I haven't been able to find a BDE
>driver but there is a standard Windows 95 FoxPro ODBC driver.

>  I'm after opinions: is it worth pursuing the option of using ODBC
>through the BDE? I have heard it is slow and my preliminary attempts
>have shown the setup to be quite cumbersome.

Brett, IMHO, you'll have to hunt for a much better ODBC driver than the
current MS one. If you use this one, you will find you have plenty of time
during most operations to shoot yourself in the head.

I haven't bought the apollo package yet, but I have tested the demo version,
and I have a strong sense that it is the way to go. Also, there is a
shareware package called ODBCexpress (oe16.zip - 16 bit freeware,  or
oe32.zip - 32 bit shareware). It is for doing ODBC stuff without the BDE. I
haven't tested it out yet, so I can't comment other than to let you know
it's there (at www.adam.co.za).

Alan

 
 
 

1. ADO-OLE DB-ODBC OPINIONS WANTED!!!!!

Hey Delphites...

I have two projects.  The first is already released (Paradox/BDE) and rather
large (200 units). The second is in design phase and could probably benefit
from client/server technology.

I've read a bit on ODBC, not much on OLE DB, and a cursory glance at ADO.
I'd like to...

1. Choose the least restrictive (as far as physical DB selection...Access,
Paradox, SQL Server, etc) for the app in design phase, and
2. port the large app to remove the BDE (and paradox later) from the
equation.

It seems that ADO would require alot of work to revamp the large app.  I've
seen a product called ODBC98 which sounds like paradise...direct replacement
of the TSession, TDatabase, TTable, TQuery with the TDatasource component
intact.  I think that it would allow me to at first lose the BDE (while
still using paradox via ODBC), and later covert to another DB format if
desired.

My question is (finally!) if I adopt ODBC as my companies strategy for the
database connect layer, will it be still be a good decision a year from
now??!!

Any opinions (especially from someone who has faced a similar decision and
is now living with the consequences) will be very much appreciated.

TIA
Frank

2. sqlturbo processes don't go away

3. Using native BDE and ODBC against Pdox tables

4. What other programs open old Lotus 1-2-3 files?

5. Problem: Using BDE with ACCESS through ODBC

6. OLE DB

7. Using native BDE and ODBC against Pdox tables

8. Connecting to Non-Pdox DBs Using ODBC/BDE

9. Using BDE in D2 with ODBC

10. Adding ODBC Driver Name to BDE using WISE

11. Would like opinions on the best venue for selling Delphi/BDE tools

12. Opinions!! Network BDE