Thanks Dennis and Tony for your helpful advice.
I am not using serial comms, so this potential problem is avoided. At this site
there would be no need for more than 3 users at one time (more like 1 or 2) with
most likely with only one at a time doing any posting.
Not sure whether the client is thin, as I have not yet met her.
I wonder why they have gone with Terminal Server, it hasn't had good press on
the list in the last couple of days.
Mark
Dennis Chuah wrote:
> Mark,
>
> Oh dear! Terminal server is Windows NT server 4.0, but with the Win station
> software licensed from Citrix. Win station allows apps to run on the
> server, but the user interface to be on another machine on the network.
> This effectively gives you a "thin client" model, where the bulk of the
> processing is done on the server, and the client is only involved in the UI.
> Eg. you can use old 386's to run you super processor intensive apps, or run
> your super network intensive apps over very slow links (like a 14.4K modem,
> although the UI can be quite slow!). As far as you app is concerned, it
> thinks that it is running on a network.
>
> You might want to consider moving to a client server database, especially if
> you expect a larger number of users than 2 or 3. You will have to be
> careful when using Paradox files over a network, and with NT, you will need
> to turn optimistic caching OFF. There is an article on Borland's site that
> tells you how to do this. I cannot remember the article off hand, but I
> will look up the URL for you. There are also certain things you will need
> to do (like making sure you have posted changes BEFORE closing tables, etc).
>
> So, the short answer is, if your app would run on NT server, then Terminal
> server is OK. If your app runs fine under an NT network for the number of
> users you support, then you don't have any consideration for terminal
> server. Otherwise, you will need to consider paradox database issues.
> Chances are that you would be OK.
>
> Just bear in mind that your app runs on the server and not the client - this
> means that the server must be appropriately sized (CPU, RAM, hard disk).
>
> Hope this helps.
> Dennis.
>
> -----------------------------------------------------
> Dennis Chuah, BE (Hons) [mailto:[EMAIL PROTECTED]]
> Manager, Product Development
> Contec Data Systems Ltd. [http://www.contecds.com]
> tel: +64-3-3580060 ext-775 fax: +64-3-3588045
>
> > I have an application D3 and Paradox which has been installed around the
> > traps mostly in single user situations on Win 95 and 98.
> >
> > I have a couple of sites where it is running on 95 peer to peer networks
> > with 3 users, and (with some very helpful advice from Gary Benner) it
> > seems to be running smoothly in these situations.
> >
> > I have now been asked by a potential site whether it will run under
> > Windows NT Terminal Server. As I have never heard of this beast, I am
> > wondering if anyone can give me a steer as to whether my system will run
> > on such a network and are there any tricks or pitfalls to watch out for?
> >
> > (Be gentle. I'm a layman!)
>
> ---------------------------------------------------------------------------
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
