Hi Myles, In the same situation we went down the DBX path and its worked well for us. TSQLQuery is a nice lean unidirectional dataset, like IBX, so its not a huge code transition. And like IBX, it seems to be fairly robust technology (in D6 at any rate, and once you're aware of a couple of known bugs).
I was asked only yesterday whether I thought it better to start a new Interbase-only application using IBX or using DBX (in Delphi 6). Although I've had good results with IBX, I recommend DBX these days, if only to avoid having to make the transition later. Cheers, Carl -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Myles Penlington Sent: Monday, February 10, 2003 3:23 PM To: Multiple recipients of list delphi Subject: [DUG]: Conversion from Interbase to SQL Server. Hi, We have a requirement to convert(?) an existing application using Interbase to use SQL Server or Interbase - we are using the IBX components currently. I see 3(2?) ways of achieving this - having ruled out using the BDE. 1. Replace the IBX with ADO components, using the same set of SQL statements etc for both SQL Server and Interbase. My only query on this is finding a good enough Interbase ADO driver/ODBC driver - suggestions? 2. Use class factories etc and have both IBX and ADO components present, using the correct set depending on the database installed. 3. Use the Delphi Datasnap/dbExpress technology (I have not used this yet or investigated it yet - so not certain if this is a starter). This needs a SQL Server and Interbase driver to make this feasible - not yet using/installed D7 Your comments, experiences and ideas are requested! Thanks Myles. --------------------------------------------------------------------------- New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] Website: http://www.delphi.org.nz To UnSub, send email to: [EMAIL PROTECTED] with body of "unsubscribe delphi" Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
