Firstly, I wouldn't use TTable in a client/server environment. It sucks up
too much resources for it to be viable. You will also likely to get
database locking issues, especially if you tried to scroll on a TTable. Use
TQuery and try to keep scrolling to a minimum - only retrieve the required
amount of data.
Secondly, you would want to watch how much traffic you generate on the WAN.
A simple two-tier application can sometimes end up generating so much
traffic that the WAN grounds to a halt.
Moving to M$ SQL server is probably just about the same effort as moving to
IB. It more of a local database / client/server paradigm shift that you
have to overcome.
You don't need the enterprise version to use either IB or SQL Server - with
SQL Server, BDE/ODBC or ADO (an add-on to the pro version) works just fine.
Avoid SQL Links as the SQL Server driver is buggy.
If you use WinFrame, your applications would run on the WinFrame server as
if they are running on a LAN. The GUI runs on the WinFrame client (on the
other side of the WAN). This might be a good short-term solution.
Regards,
Dennis.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 23 May 2001 08:18
To: Multiple recipients of list delphi
Subject: Re: [DUG]: Can D5 Pro handle it?
Thanks Pat and Nello
Couple of questions:
Is it really as simple as Pat suggests, or are there fish-hooks in there
that I need to know about?
Is Interbase inherently more reliable than Paradox?
Can I do this with D5 Pro - or do I need to buy some add-ons?
The client already uses MS SQL server for other applications, how much
bigger a job is it to convert to that?
Thanks
Mark
----- Original Message -----
From: Pat Sheehan
To: Multiple recipients of list delphi
Sent: Monday, May 21, 2001 5:25 PM
Subject: Re: [DUG]: Can D5 Pro handle it?
Sounds like a perfect application for Interbase 6. Just duplicate your data
requirements in an Interbase database and substitute your TTables and
TQueries with the IBX equivalent, arrange your security and backup and you
will increase your scalability ( and everything else ) at minimal cost.
Patrick Sheehan
----- Original Message -----
From: Mark Howard
To: Multiple recipients of list delphi
Sent: Wednesday, May 23, 2001 6:57 AM
Subject: [DUG]: Can D5 Pro handle it?
Hello
I have a nation-wide client. They are using my app at 3 sites.
They now want to centralise things and have these 3 sites plus 1 other
accessing a central database for data entry and a further 4 sites for
occasional queries.
We are talking about 2200 transactions per month possibly rising to say 4000
over the next 3 years.
The database is about 10Mbytes.
I have the system working elsewhere on LANs with up to 5 users with no
problems.
My questions are:
Is there any reason that Paradox would not continue to handle things?
Is there any reason that the existing application architecture would not
work? or would I need to convert to Client/Server?
I believe that the client has Winframe - but would there be any advantages
to using Asta to provide Internet based access to the database?
Any input would be greatly appreciated.
Mark
---------------------------------------------------------------------------
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"
