How about going with a simple web-based solution? This gives you your
central database with the aditional benefit of low bandwidth requirements.
It probably depends on the kind of data input you are talking about?
However, the head-office can get a relatively low-cost ADSL connection with
a static IP address allowing them to host their own NT-based web server
(could also look at ISDN, depending on traffic). For the kind of traffic you
are talking about you could even get away with using the free MSDE database.
Construct the application using a central Database with small stateless COM
objects (or ASP objects rather) that will provide the business layer and DB
layer. You could even use MTS if the application becomes complex enough or
you want the transaction capabilities. All your COM/ASP objects would be
talking to the database via ADO.
Code the web interface in ASP using the above objects. You could probably
easily create Reporting-type objects that will render the reports as HTML
tables based on some user query parameters.
You would probably find heaps of examples of this on msdn.microsoft.com or
msdn.microsoft/mind
On the other hand, you could code the whole lot in PHP (see www.php.net) and
MySQL (all for free) but the above MS-based solution would be more simple.
Xander
----- Original Message -----
From: Mark Howard <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Sent: Tuesday, February 08, 2000 2:28 PM
Subject: [DUG]: Application Structure
> Hi (not sure if this should be Off Topic)
> Some advice please. I want to understand:
> FIRST what is the simplest, least expensive solution that is
> *possible*
> SECONDLY what are the practical downsides of taking this simple
> option compared to the "Ideal"
>
> Situation
>
> Client has 3 sites around NZ - both islands - one site doubles as
> Head Office.
> Want each site to be able to enter data and generate reports from
> a database (same structure at each site).
> Head Office needs to be able to generate site reports and
> consolidated reports.
> NOTE: We are talking a MAXIMUM of only 60 transactions per day
> from each site.
>
> If my application is currently running with up to 5 users on a
> LAN does it follow that it should also run OK on a WAN with dial
> up lines? If not, what are the problems?
> What sort of communications setup does the client need to
> organise?
> What changes do I need to make provision for in my application eg
> do I need to upgrade to C/S?
> Is it an option have separate databases and to arrange some sort
> of consolidation each day? Prefer not to have to go this way.
>
> I've had no experience with this sort of communications at all so
> words of one syllable again please.
> Again, I Stress, I'm not after a "corporate" solution - just a
> low cost practical one. (No offence to those with "Corporate"
> names!)
>
> TIA
>
> Mark
>
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
