Interesting project. I'd agree that web access is the way to go for a few reasons, not the least of which is the ease of support for the remote users - you only need to worry about the server. It would certainly be a more long-term solution, less dependant upon the future of Winframe and the path PCAW takes down the road. It may work to your advantage as well, given the distance between you and your client. Of course, it'll mean you'll have to come up to speed quickly (and get WestWind's package immediately).

Yes, the client will have to subscribe to a local ISP, and get a static IP address (for the web server, at least). If they have access to DSL service, it's much cheaper now than it used to be.

Consider this: you could purchase and set up an NT Server with IIS at your place, do all your development right there, and give the client access to the user interface through their existing modem. Once you have it complete, just bring it to the client's site, plug it into DSL, and let her rip.

Alternatively, you could have a local ISP host the NT server for the client. It would be easier for them, but a bit more pricey. The ISP would handle monitoring the server, providing backups, and providing redundant connections to the internet. That way, the client could access the application with their current setup (although I'd still check on a DSL connection for them).

I've not yet done something like this, but am about to bring an NT Server with IIS to my home office to do this for my private development efforts. From my analysis, it's the ideal way to leverage my VFP experience to widen my market.

>A client has asked me to re-write an application because
>it is using old outdated technology that is no longer supported.
>
>Here is the background information. He has the main office
>with about 8 users on a LAN. There are about 5 users in a
>remote site (20 miles away) that need to update and query the
>data. In addition, there are 2 external sites that pay to
>query the data (these are 5 and 30 miles apart respectively).
>
>I need a low cost, minimal maintenance solution. The technique
>presently being used for remote access is 28.8 modems using
>dumb terminals (this is not a Windows app).
>
>The product I know best and can best support is VFP. Since
>the client is 3 hours away, does not have an on-site programmer,
>(I don't know SQL Server) we have virtually eliminated SQL Server as an option.
>
>Seems to me there are a few options such as:
>
>1.) PC Anywhere connection of the remote users.
>2.) Citrix Metaframe - interesting stuff, never used it and
> don't know the cost
>3.) A web enabled application.
>
>Sounds like 3 is the way to go but consider this. The client
>does not have anything more than a standard AOL account to send
>and recieve e-mail. Do you need a static IP address for this all
>to work? Can the users just dial in and connect to an intranet
>type site?
>
>Lot of options and I am looking for the pros and cons of the
>various approaches. Perhaps there are other ways to tackle this
>project.
>
>Has anyone else ever done something like this? I would love
>to hear your opinions...