> >Delphi is, ahh, "Turbo Pascal on steroids." It is a compiled
> >programming language which is able to connect to Paradox databases
> >through the same BDE/IDAPI layer that Paradox itself uses.
> Ok, so you would use it instead of OPAL? What are the advantages and
> disadvantages? Let me start... The disadvantage is you have to learn
> a new language. The advantages are....?
Actually, Ken, I wouldn't(!) use it instead of OPAL in most cases.
Delphi is considerably harder to program in than OPAL, and the language
provides you only that ... a language, and a set of data-aware controls.
When you start to look for a good, built-in report writer, the interface
features and so-forth of "a database management system" vs. "a
programming language" ... they're not there!
This is *not* a slam on Delphi, not in the slightest. But I have never
yet encountered a situation, in a database environment, where switching
to a compiled language made any huge difference in speed. As I said
previously, databases are I/O-bound not CPU-bound. If the application
is slow, then it is because the algorithm is inefficient -- not because
the runtime environment is inefficient in implementing it.
A good example of where Delphi *can* come in handy is EzDialogs
(TurboPower Software Company), which implemented a number of very useful
dialog-boxes in DLLs and made it simple to call these from Paradox.
Delphi is excellent for creating DLLs. Sometimes it's great for
implementing whole applications.
But I maintain my point ... "if the program is slow, pick a better
algorithm." (As the country song said, "there's yer trouble.")