Here's another 2c worth.

Keep one copy of your (v. low cost) Paradox database at H/O.
Get an ADSL connection for H/O (or cable modem if in Wellington).
Use tzo and assign a domain name for H/O - yourcompany.tzo.com (resolves
dynamic IP addresses - don't ned permanent IP address ~$50/yr).
Buy 3 Asta licences (~$2k).
Go into your datamodules and convert tables/queries to Asta datasets (this
is the variable bit - depends on how many programs you've got and how well
structured your data access is).
Use Asta out-of-the-box server at H/O.

Branches use 56k dial up to ISP accessing www.yourcompany.tzo.com .

It won't be super fast but at 60 per day you don't need that.

Pros - keep Paradox, keep Delphi Pro, only one ADSL required (could possibly
get away with 56k), single database, no leased lines.

Cons - if data access not clean may be a big change, not super fast.

However, when I say not fast you could download the trial from
www.astatech.com

Not a "corporate" solution - but may fit your needs.

----- 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

Reply via email to