I plan to write a project, in which the main form is in an .EXE, and this
detects the existance of various modules, which are contained in .DLL's

However, I do not want to have each .DLL conneting seperately to the
database. Is there any way in which a .DLL can share the TDatabase component
which resides on the parent form (contained in a seperate .EXE)

Also, does anyone have any GOOD replacements for the BDE?? One which acts as
a direct replacement (thus using the same syntax) would be great.... I know
the BDE has benefits, but has anyone found it cumbersome??

Comments appreciated

news:7pkeqe$gr9$1@news6.svr.pol.co.uk...
You can have a TDatabase component in each DLL, then pass the handle of the
TDatabase to the dll and assign and use it internally.
The ADO stuff in Delphi 5 looks pretty good, and as for the replacement, no
ones going to replace the main BDE functionality, that is abstracting a lot
of dissimilar databases to look almost the same.  That said, Direct Oracle
Access(yes, that's DOA ;) is terrific for Oracle, IBObjects terrific for
interbase, and I've had good luck with ODBCExpress and ODBC98 at alternate
times.  If you want the definitive comparison page, take a look at
http://www.kylecordes.com/bag/index.html
Good Luck
Mike
Have a Delphi day, I am!
Remember, friends don't let friends use VB!