Geoff,
I think there are only two possible solutions here:

1. Terminal Server/RDP
2. Conversion into client/Server app where only displayed data is shipped
up/down the wire as opposed to full indexes etc. as when using native VFP
tables.
3. Synchronise data between PC's 

Obviously Terminal Server/RDP is the easiest solution and I would recommend
the free Logmein (Logmein.com) version or Teamviewer (teamviewer.com). The
drawback is that with the free Logmein you can't remote print or file
transfer unless you pay and the app isn't expensive. With Teamviewer you can
test it out with the free version and then purchase a commercial license.
Logmein is a little slower but 100% robust and many others in the group will
recommend it. 

The C/S solution will involve you in major code/design changes I guess and
may well not be worth the time and effort.

As for the table sync option, this would seem to be a recipe for disaster if
the user isn't completely on the ball with regards to setting up FTP links
etc. and I just wouldn't go there. In addition I guess you would also have
to redesign your app considerable to allow the equivalent of batch mode
programming.

Oh, by the way, both the RDP solutions only need port 80 open so if the
client can get internet access then you are sorted.

The main cost implication on the Logmein side is that you need to dedicate
local PC to control remotely but this is a one off cost and easy to install
if you have an existing network. If you haven't got a network then the cost
of a hub and/or router is negligible anyway and the additional workstation
can be sold on as an enhancement anyway.

The trade-off is software time/effort which may well be difficult to justify
or hardware one/off cost with associated annual software licensing if
required, but the client may well be able to justify costs for "tangible
visible boxes" as opposed to your invisible programming effort! I know which
solution I would choose anyway.

Dave Crozier


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of Geoff
Sent: 20 August 2009 07:00
To: 'ProFox Email List'
Subject: Synchronising data across a WAN

I have a fairly small VFP9 app that uses local tables as it was only ever
supposed to be used by one person on one machine. Now they want two people
to use it but across a WAN with fairly small bandwidth. it works... sorta,
but performance is dreadful and it freezes so often that it is virtually
useless. Not really surprising since it is local files across net-connected
drives in another state! Sso my job is to find a solution. I've already
quoted on a rewrite into client server, but this is a large corporate so it
means that decision making is glacial and so that decision will come about
sometime afar off. in the meantime I am tasked with finding a workable
solution with the existing app. So what I am looking for is some ideas and
suggestions.

I have thought of Remote Desktop running a copy of the app on the local
server, but I cant see IT agreeing to that (and fair enough too). My other
thought is for both users to have local data and a second mini-app to keep
the data in sync. a bit messy but workable. Im just wondering if there are
any other more elegant solutions that you geniuses can come up with that can
be put into the existing app without a significant rewrite.

Thanks in advance

Geoff Flight



[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/aecf245bb82b4a489a6d1bc8a7a7f...@develop
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to