Paradox BDE to Firebird?

I've made the mistake of developing our own database application (Delphi developed) over the past seven years, without planning the database from the start. We started off with Paradox tables and the BDE engin. Problems started when the company's data grew so much, that we start having problems especially when you get to files sizes of 2Mb+ for a specific table. There's about 12 users on the network which also escelates the problem. I started looking at solutions by searching for BDE Alternatives on the Internet an my research led me to Firebird. I then downloaded Firebird and looked into converting my application and database to this. My application mostly uses TTable, DBGrid for displaying data and Filtering for realtime filtering for instance when typing a surname for the customer "van de..." It filters under the grid as you type and supports case sensitivity. This is used everywhere in the application and seems to be a problem with Firebird not supporting FilterOptions on the IBDataset and OnFilterRecord having problems with realtime display on DBGrid. SelectSQL I also could not get running in realtime. I spoke to a consultant and they recommended MySQL rather, since it also uses TTable and the BDE but according to them is much faster than Paradox. I'm pressured for time, since my business operations is slowing down to almost unworkable and need the solution that will work and can be implemented without too much hassle. Any suggestions?

I always avoided BDE and used the IBObjects (firebird native components) , this way application was faster . I think it worth a try

So IBDataset has problems not firebird it seems

Hi

I have been using Flashfiler for several years now and I am just about to make the change to Firebird. I have looked at some alternatives including MySql.

Firebird offer the BEST features for the price ($0). It is as powerful as most users would ever need, and continues to improve. The support via the yahoo group and here is EXCELLENT!



THIS aspect will apply to most (if not ALL) sql type databases. The reason being is that they do not support the same "table" based reference that you are using for your incremental search.

If you change to an sql database you WILL need to change your code to suit the database, whether it is MySql, Firebird or Interbase etc, etc.

It would not be too hard to do (AFAIK) just use an invisible component for reference source for the incremental search eg a DBCombo/DBList etc and fill the component with an sql call then use that as the index into the datatable you want to display.



DON'T do itThere is a comparison I recently read somewhere on the net. It compared MySql, Firebird and Interbase I think. FB is VASTLY better than MySql.



Yes! DEFINITELY forego the incremental search in the short term. Your clients will be MUCH happier with a FAST db than the "nicety" of incremental search.

You can add the incremental search feature as time permits and please the clients all over again

Kind regards

Peter Sanders