Hi Paul,

Thanks for the response . . .

>It really depends on what "web accessible" means to your client. Does it >mean that they want some functionality of the app available to their >customers?
YES
>Does it mean they want to be able to log in from anywhere and use the app?
YES
>Do they want to use the same app., but be able to access the data via the >web?
YES
>Until you're sure what they want, it's hard to pick one. Depending on what >the app does, what the UI looks like, what they want to be able to do, etc. >will effect the choice(s) you need to make.

The app is mainly a tracking system of widgets for the purposes of carrying out scheduled maintenances and performing service calls. As such the UI is very much a series of Data entry forms on one side and a menu of Reports on the other. There is also a totally seperate program that always runs on the server updating the data nightly - this is just a series of procedures.

. . . The Client isn't concerned whether it's viewed in a browser or a GUI. They are very security conscious and don't want to allow customers (or I think, their own Sales reps in the field) access to their LAN. I'm imagining one idea of a webserver outside the firewall calling the app behind the firewall, not sure how realistic I'm being here . . .

Blair