Board index » delphi » Translating Paradox ObjectPal to Delphi VCL

Translating Paradox ObjectPal to Delphi VCL

I've worked in Paradox ObjectPal and am trying to move some
applications to Delphi. Are there any FAQs or other resources that
would help with rough equivalents in the two languages?

For example, in a Paradox Form object the Object Explorer offers
standard built-in methods (e.g., action, arrive, depart, canDepart,
canArrive, etc.) each of which executive automatically. In Object
Pascal how do you control for code that executes when focus moves to
an object versus code that executes when focus leaves an object?

Second example, is there an equivalent to TCursor in VCL?

Anything that you think would be helpful would be greatly
appreciated.

Thank you,

Bill Braun

 

Re:Translating Paradox ObjectPal to Delphi VCL


Hi Bill,

I changed over from Paradox/ObjectPal to Delphi about a year ago, and
haven't found the transition too difficult, though in general I'd say Delphi
is somewhat more complex, but a lot more powerful, also more robust.

Quote
James Roberts <m...@privacy.net> wrote in message

news:3AB9F031.3C153E4A@privacy.net...
Quote

> For example, in a Paradox Form object the Object Explorer offers
> standard built-in methods (e.g., action, arrive, depart, canDepart,
> canArrive, etc.) each of which executive automatically. In Object
> Pascal how do you control for code that executes when focus moves to
> an object versus code that executes when focus leaves an object?

The events on the Delphi object inspector (same idea as Paradox built-in
methods) are pretty well documented - the Delphi on-line help can be a bit
daunting, but if you hit F1 on the event you'll end up where you want.  Be
warned though that there are not many (if any!) exact equivalents.

Quote
> Second example, is there an equivalent to TCursor in VCL?

The TTable or TQuery objects on the data access tab will do everything that
a TCursor does, and are normally placed either on a form or on a separate
TDataModule, along with TDataSource objects.   TDataSource provides a
conduit between them and visual DB components, and also has a couple of
events of its own.  In order to keep actions 'in the background' as with a
TCursor, you can use the TTable or TQuery DisableControls and EnableControls
methods.

Good luck!

Ruth

Re:Translating Paradox ObjectPal to Delphi VCL


Many thanks, Ruth.

Bill Braun

Quote
Ruth Buckner wrote:

> Hi Bill,

> I changed over from Paradox/ObjectPal to Delphi about a year ago, and
> haven't found the transition too difficult, though in general I'd say Delphi
> is somewhat more complex, but a lot more powerful, also more robust.

snip for space

Other Threads