Frickler

As you always need to acquire the newest Delphi version in order to get bugs fixed on FireDAC, why not try a third party DAC? DevArt IBDAC can convert from BDE, IBX and FibPlus. Never needed to convert, so I cannot say how well this works though. But you can download a trial version and try it for yourself.

There is a commercial add on to Indy called YuOpenSSL, that replaces OpenSSL DLLs with Delphi DCUs.

IBX2 for Lazarus can do that. DevArt IBDAC can't.

Syntactic sugar. It does nothing more than that begin-end, but makes it clear (to me) that "B" is defined only for the purpose of abbreviating that expression.

Do you really need A? As you can have for var i:=1 to 10 do ... why not with var B := dmStoreInventoryData.tblUpdateItemForStore do begin B.AppendRecord([1,'foo','bar',3.1415]); end; and "B" would only be visible inside the "with" block, not outside of it. Currently you have to "fake" it by begin var B := dmStoreInventoryData.tblUpdateItemForStore B.Edit; B.FieldByName('Qty').AsInteger := NewQty; B.Post; end;

Both compile Pascal to javascript using pas2js. This seems to be more like UniGUI, Kitto or even IntraWeb, where your program itself is a webserver.

You mean Simula. Modula had no classes. Btw. Anonymous functions have been a feature of programming languages since Lisp in 1958. That was really a long time ago.

Maybe this is why it's named "Interbase Express" and not "Firebird Express"... Do you do low level access to Firebird? There is a low level Firebird interface API for Delphi and Lazarus from MWA Software (https://www.mwasoftware.co.uk/fb-pascal-api). It provides comprehensive documentation including a guide to write UDRs with pascal.

DevArt UniDAC supports MongoDB (dunno how well, never tested it). mORMot supports it too (https://github.com/synopse/mORMot2).

Until 2005 we used to use QuickReport Pro with QuickReport Designer, which was very buggy at that time. So we tried ReportBuilder Pro. It was very stable, had great documentation and lots of useful features. But it was so slow. Printing a report took more than ten times as long as with QR. Then we tried FastReport - and never looked back.

Hmm... 50 columns? So why not concatenate all of them and get the combined length, subtract this from 50 * 5 (length of "False") and you get the count of "true".

Have you tried ADO ("dbGo") instead of FireDAC?

If you don't need to access Paradox, only DBF, you can try TDbf. See If you need SQL queries, use FireDAC LocalSQL witf TDbf.

Hi all, is FireDAC extensible, so that I can add a custom database driver, e.g. for Absolute Database?

...would require GROUP BY, and then problems arrive with "AA" and "BB" not being grouped.

The User Table is named MON$ATTACHMENTS See https://firebirdsql.org/file/documentation/chunk/en/refdocs/fblangref30/fblangref30-appx05-montables.html#fblangref-appx05-monattach

FireDAC doesn't support Paradox at all. You have to port to another Database, e.g. Firebird. But beware, no more SetRange and Filter, but SQL only.

I don't think so. I think InterBase is designed to be very slim and fast. For example, for everything except the most essential internal functions you have to use UDFs. Furthermore, it looks to me that the main use case is still embedded SQL like in ye olden times of InterBase on UNIX.

With Update 2, Interbase 2020 has now CTEs.

Don't add "Port" and "Protocol" if using embedded.

Interbase has virtually no internal functions. Not even in the newest versions. All has to be done in UDFs. The Firebird developers on the other hand had changed that from the beginning.

Full support including the new 128 Bit types, timestamp with timezone and the new batch API for INSERT/UPDATE? I ask because UniDAC/IBDAC only supports a subset at this time.

Using SQL, it's slow. But Absolute Database isn't made for SQL, but for good ol' ISAM: IndexName, SetRange, Locate, Filter, you name it. There (and in single user mode) it is really fast. And you not only don't need any DLLs to access it, you can even embed the database into the EXE (for read only databases such as catalogues).

But interposers did.

It's possible that Interbase supports only "simple case", that is case foo when 1 then 'one' when 2 then 'two' else 'many' end