Hi John,

I'd say that a major factor in such a decision is WHO uses the application.

If it is within a single company, and they agree, then it's a no-brainer.

But if it's an application used by many different companies then I'd say the major hurdle is DO THEY TRUST THE INTERNET.

A client here recently had no internet access for over a week, caused primarily by a clerical error where the bill for the service was forgotten. I was most happy that our application is not web-based < s >.

Some clients may be apprehensive about having THEIR data stored somewhere else. And I guess it's possible that those who would agree to that would have major security stipulations in their agreement. Of course this depends entirely on the nature of the data.

Good luck



>I have an application used in facilities around the country (USA).
>
>Basically there is a server in each facility. All the data for the app resides on that server. Workstations run the executable locally accessing data on the server. Albeit rare, some workstations are accessing the server via a WAN. Most are on a LAN.
>
>My question: Looking at the big picture and trying to make decisions about the future of my app, I feel I should look into one central database on a server and users accessing the data via the net. How would I make thse decisions? Whom or what literature would I consult to put together a set of questions that would help me determine this?
>
>Thanks,
>John