Re: [DUG]: Can D5 Pro handle it?

[Mark Howard]

Bit more background on my app.   I use NO DB aware visual components. ALL of the DB access components are on two Datamodules, one for 30 TTables and the other for 25 TQuerys (although I now realise that I can probably do with a fraction of those TQuerys) The TTables are opened and closed as the app opens and closes. Tend to use the TTables for filtering, lookups and editing tables and TQuerys for selecting data for reports. I do not use alias'.  I reference the database directly by path name. DO use some autoincrement fields.   Given the above then, does that alter the flavour of any of the advice? Given Nello's last post regarding WinFrame, would it be better to "Suck it and see" with Paradox? If not, would it be possible to create a Development copy of the project in which I replace the two TTable and TQuery datamodules for a couple using IBTables and IBQuery's - with the intention of leaving everything else pretty much unchanged (autoincrement filds excepted)?   I realise this is old hat for most of you - but it's brand new to me. I mean - what I'm also wondering is this:  If my current application using Paradox is single tier, does converting it to address, say Interbase, make it a two tier system?  I suspect not.  So what has to happen for it to be called a two tier system? and when do I suddenly need Enterprise?   Mark ----- Original Message ----- From: Nello Sestini To: Multiple recipients of list delphi Sent: Monday, May 21, 2001 6:52 PM Subject: Re: [DUG]: Can D5 Pro handle it? Is it really as simple as Pat suggests, or are there fish-hooks in there that I need to know about?   i think it depends on how your app is organised.   it CAN be almost mindless for the "right" sort of app.   Is Interbase inherently more reliable than Paradox?   emphatic yes Can I do this with D5 Pro - or do I need to buy some add-ons?   take a look at Interbase Objects components.   (IBO not IBX).   IMO they're well thought out.    They also share class hierarchy with BDE DB-aware components.    At one time (perhaps still - i haven't looked in a while) IBX wasn't like this and converting as a lot more trouble because of it.   The licencing on them is also interesting - "Trustware".   You pay for them if you use them to make a profit.   http://www.ibobjects.com   The client already uses MS SQL server for other applications, how much bigger a job is it to convert to that? others on the list here are more active with MSSQL than I am so i'll defer.   given the price of IB6 and the quality of the IBO components I'd still give IB a look though.   -ns