N,
> dataaware is a nightmare with C/S databases - avoid it like the plague. IT
> does work tho, its just not that quick. If you switch from paradox, you
> _have_ to get out of the locate/findkey/next/prev etc mentality REALLY
> quickly.
Yeah I realise that. We use ADO / SQL2000 for some other stuff so I am aware
of that..... ;-) The data aware bindings would only be to queries / stored
proc's where the datasets are small......
Thanks for the info.....
------------------------------------------------------------------------
--Donovan [[EMAIL PROTECTED]]
Donovan J. Edye [www.edye.wattle.id.au]
Namadgi Systems, Delphi Developer [www.namsys.com.au]
Voice: +61 2 6285-3460 Fax: +61 2 6285-3459
TVisualBasic = Class(None);
Heard just before the 'Big Bang': "...Uh Oh...."
------------------------------------------------------------------------
GXExplorer [http://www.gxexplorer.org] Freeware Windows Explorer
replacement. Also includes freeware delphi windows explorer components.
------------------------------------------------------------------------
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Nic Wise
Sent: Friday, 3 November 2000 12:04
To: Multiple recipients of list delphi
Subject: RE: [DUG]: [Q] Lightweight DBMS....
Donovan,
have you considered interbase? (what did anyone else expect me to say!?)
It fits almost all of the criteria:
> - Extremely hostile and remote. ie. Applications are running on machines
> that are very difficult to access either physically or with remote access.
fine.
> - Machines are prone to being abused ie. powered down due to
> power failures
> etc.
tick. As long as the OS can handle it too.
> - Machines are used for "real-time" applications such as providing data
> capture for live sporting events
fine.
> - DataSets are "smallish" +/- 20 tables with some tables having +/- 5000
> records
even better.
> - DB access is multi user with an upper max of +/- 10 concurrent users
even even better.
>
> At present we have our apps running using Paradox / BDE. Naturally we have
> our fair share of corruptions etc. So we are looking for an
> alternative that
> would satisfy the "Holy Grail"
>
> - Not require the deployment of DLL's for data access (a la BDE)
hm, maybe not. you need to install the server on the server, and the client,
which is pretty much gds32.dll I think, on the clients. Not hard by any
means.
> - DB should be self healing to fix corruptions etc.
Is this possible? IB has gfix, but I'm yet to come accross a corruption
myself.
> - DB should allow easy restructuring should the data definition change
its SQL. Not easy, but possible. You should be using a CASE tool anyway :)
> - Still provide SQL access to the data
only way to get it....
> - Provide TDataSet interface so that existing DB aware controls
> can be used
> easily
IBX or IBO provides this.
> - How do these products stack up in the real world? ie What have been your
> real world experieces?
Works well.
> - How well do the products scale in a multi-user environment?
very well, up to about 20-50 users on intel hardware.
> - How well do the products scale as database size increases?
fine, biggest I know of in NZ is about 3-5gig, biggest overseas is about 30.
I think.
> - How well have DB aware controls worked. In particular the Dev
> Express (esp
> Quantum Grid) components?
dataaware is a nightmare with C/S databases - avoid it like the plague. IT
does work tho, its just not that quick. If you switch from paradox, you
_have_ to get out of the locate/findkey/next/prev etc mentality REALLY
quickly.
N
---------------------------------------------------------------------------
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"
---------------------------------------------------------------------------
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"
