>
> > Option 1 will be cheaper but will need more programming.
> > Option 2 will be more expensive but probably less error
> > prone and less programming.
>
> I think your assessment of the two options is mostly correct, however
> I would add an additional advantage to option 2: flexibility. That
> option will give you much greater scope to add other functionality and
> features in the future. **IF** this option is viable to you client
> (if they can justify the cost) then it really is the best solution.
> With such a network in place they can even consider inter-office
> messaging etc.
>
> As an option 3...
>
> My major client has 6 branch offices. We setup a frame-relay network
> between the branches and the head office and installed MS terminal
> server in the head office. The branches are all permanently connected
> to the head office, their actual desktop sessions are running on the
> head office terminal server (with only screen and keyboard updates
> traversing the network). This has some really nice advantages...

I worked previously with a company that implemented NT Terminal Server I
loved it especially after a power failure. You would log on and it were as
if you were never gone.
However here in Darkest Africa :-) most of us(clients and me) cannot afford
leased lines or permanent connections.
If I consider option 2 do you have examples/demos that demonstrate how to
cache data temporarily. How to work with an unconnected dataset that
contains data. Also any design tips will be appreciated. I have never done
something like this so I dont know what components to use. I suspect that
there is most probably such a demo in ibo already.

Groete
Gerhardus
PS
Thanks for the swift response.