Re: REPOST-MSOffice manipulation w/ WebPage or SmartClient?

Here are a few comments that may help you with your design or point you
in a better direction:

In a closed environment where everyone is using Windows and has the
..NET Framework, then a smart client is almost always a better solution
than a web page. Web pages are only good for two things: displaying
read-only information or providing an interface that can be usable
across multiple operating systems. If you have a Microsoft
environment, then use a smart client using no-touch deployment (NTD).
NDT may be called by other names, but searching for "no touch
deployment" or "NTD" will give you information about this type of
deployment. NTD will allow you to distribute a Windows Forms
application like a web page; someone would simply type the URL or click
on a web page link to access the application. (You may need to adjust
the client's .Net Security settings to allow the application to
execute.)

If you are going to manipulate the Office document on the client and
want to use web pages, then you could perform this task on the client
using JavaScript. The security policy on the client would need to
allow the creation of ActiveX controls via JavaScript, using the
ActiveXObject. For the Office document's location, you would use the
web path, such as http://MyWebServer/MyDocument.doc. Here is a link
for the description on the JScript object:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/js56jsobjActiveXObject.asp

I do not know the type of application you are building, so a web
application may be the best solution. However, you may want to
consider Windows Forms instead of web pages: create a windows
application, deploying it via the web using NDT. However, the client
machines will need to have the Office PIA installed and may need their
security settings adjusted. Though, if you still want to use web
forms, then you could use a .NET assembly embedded on the web page
using the <object> tag, using JavaScript to access the .NET Object.


Catch you later,

Boyd

.

Relevant Pages

  • Re: REPOST-MSOffice manipulation w/ WebPage or SmartClient?
    ... In a closed environment where everyone is using Windows and has the ... then a smart client is almost always a better solution ... then use a smart client using no-touch deployment. ... NTD will allow you to distribute a Windows Forms ...
    (microsoft.public.dotnet.general)
  • Re: VB Express vs. ????
    ... AND your target audience is Windows OS based, then "click once" is they way ... the client PC. ... Since these are Windows forms apps you can ... deployment of applications and the web side will return to a more simple (as ...
    (microsoft.public.dotnet.general)
  • Windows 2003 CA in W2K Domain
    ... I am planning a deployment of certificate services for a client ... The client has a Windows 2000 domain but will migrate to 2003 at ...
    (microsoft.public.win2000.security)
  • Re: Windows 2003 CA in W2K Domain
    ... I am planning a deployment of certificate services for a client ... > possibilities of deploying Windows 2003 certificate services in this ... The key is applying the Windows Server 2003 Schema. ... (subject to the client OS versions). ...
    (microsoft.public.win2000.security)
  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
Quantcast