Time to move on from BDE, ADO or dbExpress.
Originally shared by Delphi
Learn All About Accessing Databases with Delphi and FireDAC in this fantastic webinar replay by Pawel Glowacki.
#Android #iOS #macOS #Windows10 #Linux #developer
13 thoughts on “Time to move on from BDE, ADO or dbExpress.”
Sadly ClientDataset and the Provider are still needed in some cases due to limitations in FireDAC. Would love to ditch them completely.
Asbjørn Heid What about TFDMemTable?
docwiki.embarcadero.com – FireDAC.Comp.Client.TFDMemTable – RAD Studio API Documentation
Lars Fosdal Nah, more to do with lacking Aggregate support and no Before/AfterUpdateRecord events.
Oh yea and not really supporting calculated fields if you want to avoid specifying all the FieldDefs from the query manually.
BTW TClientDataSet is not working on Linux because midas library is missing.
Maybe is deprecated?
I have a lot of code with ClientDataSet.
Are the QP posts for these lacking / non-functioning features?
Lars Fosdal unfortunately yes (22 dec 2016).
Because this I think ClientDataSet is deprecated.
quality.embarcadero.com – Log in – Embarcadero Technologies
I started with BDE then moved to DBX and now UniDAC and TClientDataSet for non server things.
I’m not sure if in the future to change TClientDataSet with TFDMemTable (very similar) or a more radical one. Maybe SQLite (with UniDAC).
Lars Fosdal I have a few pending, need to take some time to write them down/make reproducible cases.
Does it support dBASE files?
Thomas Mueller FireDAC? Sure, over ADO->ODBC. Which is tricky, because as long you have BDE installed, it takes over the dbf handling. Once you uninstall it (or goes live on client pc without BDE), it will be served via the windows drivers and everything changes.
Unidac has been great for this for quite sometime.
TClientDataSet is not working for Linux. It is somehow deprecated?
No, we only forgot to ship the matching shared object file
You must log in to post a comment.