Nice idea - check the IB license tho - it specifically mentions connection "reuse" systems ala MIDAS - you still have to license by USER, not by CONNECTION.
 
Natch, IB6 gets rid of THAT little problem.
 
N
 

--
Nic Wise - [EMAIL PROTECTED] / Inprise/Borland New Zealand
main line: 09.360.0231 / ddi: 09.360.6713 / cell: 021.676.418

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jeremy Coulter
Sent: Tuesday, 25 July 2000 11:09
To: Multiple recipients of list delphi
Subject: [DUG]: Suggestions or comments...

Hi all.
We have a situation here where we have an NT service and a normal DB Application that both use Interbase.
The problem we have is that the NT Service chews up an IB lic. when it is in use...i.e. all the time.
this then means we would have to get an extra client lic. which is not really all that great for the client, since its not really their problem, and we dont want to carry the cost of an IB LIC every time we sell our product.
 
SO, the solution as I see it is this, that we develop an app. that acts as a data-broker.
This would obviously cause SOME issues for us, but would solve the problem as I see it.
 
The question I am wanting an answer to is, we dont have Midas which would be the way to go I think, SO I have been thinking along the lines of using a DCOM server to do the data-brokerage for the NT service and the DB application.
This would be fine for the NT service, but it causes a number of issues for the DB Application, i.e. we use tables and querys etc.
Would we best to buy Midas.....or rather we need to get another delphi anyway so we sould look at getting the version of delphi that has Midas.
 
Can anyone comment on the above ?
Am I going down the wrong path ?
Will midas help us with the problem of needing to use tables datasets and storedproc componetns etc. ??
 
Cheers,
 
Jeremy Coulter (Software Development Team Leader)
Triton Commercial Systems
6A Burdale Street
Riccarton
Christchurch
( +64 3 3483973  Fax +64 3 3431613
 

Reply via email to