When people ask for "entirely web-based" in an intranet environment, you need to ask them what goal they're trying to achieve by that requirement. Are they trying to ensure that the app will be equally usable by Mac and Linux and AIX and HP-UX clients, as by Windows clients? Or are they after buzzword complience?
If it's "no-touch deployment" that they're after, you need to ask whether you're supposed to be re-implementing the word processing parts (that MS Word already does very well) as a web-based app, or whether they want you to finish this century. In my opinion, the "entirely web-based" requirement is not consistent with wanting to use Word document templates as part of the app. I think your questioning of that rather contradictory pair of thoughts is quite appropriate. As others said, you would only use Word on the client -- controlled by a "smart" AKA "fat" client -- a .NET executable. Good luck. At 10:30 AM 12/26/2004, Jeff Little wrote (in part) >... they have about 150 Word document templates that they use to generate >various documents in the course of a project. They want the generation of >these documents to be reasonably automatic. [snip] >Part of the requirement spec was that the application should be entirely >web-based. [snip] J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
