Subject | Component structures |
---|---|
Author | tvdien@ymail.com |
Post date | 2011-07-28T22:49:36Z |
Dear all,
I'm quite new to Delphi (database) development, especially using Firebird. However, I already managed to get involved in a project to convert a suite of BDE/Paradox applications to it. These are meant for a multi-user network environment (currently pretty slow).
BDE/Paradox had a pretty straightforward structure; just put a TDatabase and a TQuery on a form, or even just a TTable, together with a DataSource, and there you are.
With IBO/Firebird, however, I'm getting confused. There's so much to choose from and I have no idea what the pros and cons of each are. TIBODatabase, separate IB_Connection(s), Transaction(s), all sorts of properties, ClientDataSet(s)?
What I'm looking for is some guidance as to what are the most important things for making the conversion as straightforward as possible, and how to go from there to benefit most from what IBO/Firebird has to offer.
Thank you so much.
I'm quite new to Delphi (database) development, especially using Firebird. However, I already managed to get involved in a project to convert a suite of BDE/Paradox applications to it. These are meant for a multi-user network environment (currently pretty slow).
BDE/Paradox had a pretty straightforward structure; just put a TDatabase and a TQuery on a form, or even just a TTable, together with a DataSource, and there you are.
With IBO/Firebird, however, I'm getting confused. There's so much to choose from and I have no idea what the pros and cons of each are. TIBODatabase, separate IB_Connection(s), Transaction(s), all sorts of properties, ClientDataSet(s)?
What I'm looking for is some guidance as to what are the most important things for making the conversion as straightforward as possible, and how to go from there to benefit most from what IBO/Firebird has to offer.
Thank you so much.