InfoPath Dev

Well, as far as disabling undo/redo, you can do some things programmatically. The OnBeforeChange event (IP2007 OM, equivalents exist in IP2003 as well) is cancellable and has the IsUndoRedo flag. You can check this flag and do things when it's true. For example, this will effectively disable Undo/Redo: public void ...

If you are writing this in javascript on the page that hosts forms server, you could inspect the data tree (say, in your onunload handler) and find out if the data is dirty or not in the following way: // Checks if user actions have changed data function CheckIfDirty() {  var objViewDataNode;  // Get the root of the data ...

Depending on what you're trying to acheve you can use the count function instead: count(preceding-sibling::my:<RepeatingGroupNodeName>) + 1 For example, this can be used to give a repeating table alternating-color rows

AFAIK, you need MOSS to use InfoPath Forms Services. Also, not all MOSS SKUs will necessarily have it (I think Enterprise has it but I do not know much about the SKUs/licenses).

Exacte! J'aurais dû d'ailleurs le mentionner. Désolé, je n'ai pas de version française d'InfoPath donc pour moi c'est difficile parfois d'imaginer comment l'interface se traduira-t-elle :)

Il y a un moyen de le faire, mais ce n'est pas évident. C'est vraiment une astuce qui utilise un détail d'implémentation de la fonction eval (qui n'est pas propre à XPath mais qui est plutôt une fonction introduite par InfoPath même).  Il y a un bon article sur le blog de l'équipe InfoPath qui décrit la solution (en ...

I tried to see how userName is implemented via reflector but it seems like the most interesting bits are obfuscated :) Nonetheless, I was able to dig out this: return SPControl.GetContextWeb(HttpContext.Current).CurrentUser;   This may give you the idea of what is going on... also, like you have mentioned, you might want to make sure that ...

Hello Claire, I will make a couple of comments here that will maybe help you out: 1. FullTrust is not always needed for IP2003 solutions with code. It depends on what your code is - if you do not use anything that requires full trust (such as writing to disk) you can use domain trust instead. Domain trust does not require an MSI installer. 2. ...

Unfortunately you really have to rewrite your code - Forms Services requires you to use C#/VB.NET using new object model.

As far as I know you can have several SP sites (as subsites) on the same port. For example, that's how personal sites work. For using ports other than 80, I am not sure why you cannot publish. One thing I can suggest (a short in the dark, really) is to publish the form as a feature via Admin deployment (this is done in SharePoint Central ...