A couple of things:
1. Just thought I'll throw another idea for you-- why don't you write your
app as a web server. That way, all you need is for the web server to run on
one of your NT workstation boxes (ought to be able to server up to 10
connections). You have only one database connection (which is your web
server), and can throw MIDAS, etc. into the too hard / too expensive / too
complex basket. Your webapp can cache realtime data to serve out to the
clients. There are various technologies that you can employ to push data to
the clients. Also, no need to worry about installing client software
because they will all be using the browser.
2. Database backend should not be an issue for you. You ought to make your
code independent of the database backend, for example, in case the database
vendor decides to drop the product. It is not difficult to do, if you
structure your code well.
For all Nic's and Tony's rant about SQL server, it has worked fine for us -
and we do not have any DB admin expertise at all. You can compare features,
argue about merits till hell freezes over, but at the end of the day, all
that really matters is that the solution you provide meets your client's
needs. For us, SQL Server works straight out of the box. No tweaks, no
weekly reboots, etc.
My point is, I am not saying that IB is no good or does not work, but I
cannot understand what all the fuss about SQL server is about as it has
worked very well for us and that is all that matters.
Regards,
Dennis.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
