Garrett
>Think of it as an Intranet technology, and it might look better to you.
My current Intranet work (biggest site >600 computers, >1000 users) uses any frame- and java1.0-compliant browser with Java/HTML frontend and VFP as a middle tier. Client Implementation: zero. Extra client implementation if users upgrade to Win98 or WinNT: zero. Browser dependence: zero. Extra client implementation when the ole server is upgraded to VFP6: zero. That won me the sale. An intranet technology that forced my client to implement on all those clients and use a Browser I specified would have lost me my biggest sale- they would have implemented a standard C/S solution from the opposition.
To be honest, if you have to implement locally, I'm not sure what benefit Activedoc offers over standard C/S products and update scripts.
Am I missing something?
>Actually, DHTML _does_ specify browser to an extent:
Sure. But if you use something like Dreamweaver, you get code that checks the Browser and makes sure the appropriate stuff happens.
Regards
JR
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
