Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / General MS InfoPath Questions / January 2007

Tip: Looking for answers? Try searching our database.

Convert an InfoPath form into Word Document

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ridawg - 15 Nov 2006 13:44 GMT
Just read the article by S.Y.M. Wong A Ton on converting an InfoPath form
into a Word document. I have a need to do this for several existing forms.

My question is in the article jscript is the programming language used and I
was wondering if I could use vbscript instead? If so can someone provide an
example?

The reason I'm asking is my existing forms are all using vbscript so I would
like to stick with that versus having to re-create these forms using jscript.

This would be a huge help - Thanks!

Signature

-ridawg

S.Y.M. Wong-A-Ton - 16 Nov 2006 04:58 GMT
Yes, the lines can be translated to VBScript almost one-on-one. Here are some
pointers to help you get started: Remove the semi-colon at the end of each
line, replace "new ActiveXObject(...)" with "CreateObject()", replace "var"
with "Dim", declare and assign variables separately, and use "Set" when
assigning values to objects. This should get you on your way.
---
S.Y.M. Wong-A-Ton

> Just read the article by S.Y.M. Wong A Ton on converting an InfoPath form
> into a Word document. I have a need to do this for several existing forms.
[quoted text clipped - 7 lines]
>
> This would be a huge help - Thanks!
ridawg - 20 Nov 2006 13:10 GMT
Great - thanks for all the help!
Signature

-ridawg

> Yes, the lines can be translated to VBScript almost one-on-one. Here are some
> pointers to help you get started: Remove the semi-colon at the end of each
[quoted text clipped - 15 lines]
> >
> > This would be a huge help - Thanks!
S.Y.M. Wong-A-Ton - 22 Nov 2006 06:14 GMT
No worries. :)
---
S.Y.M. Wong-A-Ton

> Great - thanks for all the help!
>
[quoted text clipped - 17 lines]
> > >
> > > This would be a huge help - Thanks!
ridawg - 27 Nov 2006 15:29 GMT
Just started working on this - I was side tracked for a little bit.

I've run into a couple of problems and I'm sure you can help me out.

First, when I convert my formatted XML form into XSL using the Transform
Tool I get the following Dialog box - Multiple namspaces were found in the
document (the namespaces are listed and I can select them both or one or the
other)
1.
http://schemas.microsoft.com/office/infopath/2003/myXSD/2006-11-27T14:41:33
2. http://schemas.microsoft.com/office/word/2003/wordml/sp2

I've selected them both and each one separtely but I still can't get this to
work.

The following is the error I get when I actually click the button I've
created.
Object required: '[string: "<?xml version="1.0" "]'
Line 34

Line 33 & 34 are the following:
Dim formInWordML
set formInWordML = formInXML.transformNode(xslXMLToWordML)

I've created a very basic form. Just 3 fields. I'm just trying to get this
to work in VBScript before I try to use it in my more complicated forms.

Thanks for the help!

Signature

-ridawg

> No worries. :)
> ---
[quoted text clipped - 21 lines]
> > > >
> > > > This would be a huge help - Thanks!
ridawg - 30 Jan 2007 19:49 GMT
I figured out how to do this (solved the namspace error and converted S.Y.M.
Wong-A-Ton jscript code to vbscript). Please see the other post I created on
this topic. The other post is called "Convert InfoPath to Word".
Signature

-ridawg

> Just started working on this - I was side tracked for a little bit.
>
[quoted text clipped - 50 lines]
> > > > >
> > > > > This would be a huge help - Thanks!

Rate this thread:






 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.