I haven't dwelled in the kingdom of Microsoftian tech for a while so i'm not able to help you there, but if you ask how to send a XML or plain text file to a site (elaborate here on exactly what you want to do) in a asp.net community forum you'll probably get some good solutions. And a XDP file can ...

That is a 2 way stick.The why you should change the Mime type is that the associations File Type --> application in most OS is done by Mime type.But, this also means that a end-user migth create the association of your Mime type to LC:Designer and puft, your system failed.Apart from randomizing the ...

Why do you feel the need to do that?What problem do you have or what do you want to do that makes you think you have change the Mime type of the file?

I would say your best bet was to have 12 different templates (XDP) and your orchestrated process picks with template to use based on an input variable.AFAIK XFA.forms don't support multiling implementations or internationalization processes. This and the fact that most of your document is made of no...

You can have 2 text boxes, one for the user input (no caption) other for the label (here the input section is not visible because you'll set the width to 0). This way you can get the tool tip on the label only. For the end user this will be transparent.

The object you want the tool tip to be in must be editable by the end-user, otherwise the tool tip won't be displayed.Try to check if that is the case.

One way to do it (based on Angel's link) is:First you have to set up an External Authorization Handler in order to be able to act on the print event of a given document. To do so, you can follow the Print Once External Authorization Sample that Adobe provides (see Angel's link). Compile it, build t...

It might.If it doesn't, post your form so i can have a look at it.

Livecycle is more than capable of that.The problem is that if you use reader 9 or above you won't be able to work well with your form.If you use reade 8 or below, no problem then.

On the object you don't want to appear in the print version goto properties and on the presence attribut choose visible - screen only.