The best advice I can give you (one that I ignored) is to replace all
(or most) of the tables with tqueries. The second bit of advice is to
not use the default transaction and ensure that you understand the
transactions as they are different to paradox. This applies to firebird
and interbase.
What you can do is to use a char field holding either Y/N or T/F.
Alister Christie wrote:
I'm in the process of converting a significant application off
BDE/Paradox to probably firebird. I'm looking at methods for doing
this in a semi-automated way. I had thought a good interim step would
be to get the application running on BDE/Firebird via the Interbase
driver in the BDE. I'm trying to do this in a way that the
application can run on both paradox and interbase, but I have hit a
problem with a number of paradox boolean fields. Okay that's probably
enough background...
So my question is there a way to get a paradox/interbase field to map
to a TBooleanField on a TTable?
--
*Rohit Gupta*
* B.E. Elec. M.E. Mem IEEE Associate IEE*
*Technical Manager*
*Computer Fanatics Limited*
**
*Tel* +64 9 4892280
*Fax* +64 9 4892290
*Email [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>**
*Web *www.cfl.co.nz <http://www.cfl.co.nz/>
------------------------------------------------------------------------
This email and any attachments contain information, which is
confidential and may be subject to legal privilege and copyright. If you
are not the intended recipient, you must not use, distribute or copy
this email or attachments. If you have received this in error, please
notify us immediately by return email and then delete this email and any
attachments.
_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: [email protected]
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe
