InfoPath Dev

Well..dang if it still needs to be published, ( hence having InfoPath client on some machine in the production domain), it's not even worth it ( to me at any rate) having to go into Visual Studio, learning all that stuff bla bla bla. I mean it's really simple deploying after it's published.... .{ copy to network, Verify, ...

Our production environment(s) do allow for Office Products, that being Word, Excell, Acess and so forth. They ( the admins of the networks ) haven't gotten around and or thought the use of the InfoPath client program was and or is needed. PureEdge Forms is currently implemented and used. I work on Government {DoD} systems / ...

Ya...that's what I figured...damn.  Ya know one would think the Microsoft designers / developers of that application and or Bill Gates & company would of thought about that. In so far as, not all production environments { like ours } allow "development tools" to exist in the target domain a product ...

That doesn't work with the publishing wizard. When I put in the URL of a different server ( that's not in the same domain as my developement machine) the wizard errors out because it's trying to connect to the URL of the path I put in. Which is what I would expect.  You see what I'm saying?

I've created this form template on my development machine in a virtual environment. It all works well and good. The plan is to eventually use this Form on a MOSS server in our Production environment. In my development environment, I publish the form / Upload the Form etc....using the Virtual machine names of course. In the publishing ...

I figured it out myself...well...and little help from google and http://office.microsoft.com/en-us/infopath/HP101000931033.aspx?pid=CH100598401033 duh huuuh... The short of it was, initally I was publishing the form to the MOSS server. When in fact I should of been publishing to a file system Network location. Did that, pointed the ...

Trying to publish a browser enabled form with some code behind. The "Design a form template that can be opened in a browser or InfoPath" checkbox IS checked in the designer. There are NO "Compatibility" errors.  I go the Central Admin site, to the "Upload Form Template" section, and "Verify" the ...

Okay...that all makes sense.  Actually all the business about relative vs absolute was a previous problem I was having, which I fixed from a MS Exchange hotfix. Prior to this rendering issue, I couldn't even open up the email message being generated and ultimately sent from Exchange. It was a MOSS 2007 / Exchange 2003 ...

Well..why does it work with Word Documents.  You know what I mean?  If I create a Word doc in a library....set an alert for new items, when I recieve the email and  I can click on the link in the email and the word doc comes up. Is that because IE and Word are integrated together more so?

Have this browser enabled form as a content type in a MOSS 2007 document library. There's an alert set up for when new forms are saved to the library, an email is generated and sent to a user. The email arrives indicating a new item has been added like I expected it to. In the email, there's a link to view the newly created form. However ...