InfoPath Dev

Malheureusement, je crois que le meilleur moyen serait de modifier chaque formulaire existant et de le rediriger vers BETA. Chaque document InfoPath contient un attribut href qui pointe vers le modèle (ALPHA dans ce cas). Il s'agirait alors de le modifier pour le pointer vers BETA.

Here is a pretty good MSDN article to get yourself started: http://msdn2.microsoft.com/en-us/library/ms406041.aspx Note that you can only do it with InfoPath 2007 and not 2003.

My only suggestion at this time would be to check the server event log and the Sharepoint logs to see if there is a better error message than just "updating failed"... This thread has instructions on how to get to the Forms Server logs: http://www.infopathdev.com/forums/p/5513/20653.aspx#20653  

Hello! Unfortunately, there is no easy way to achieve what you are trying to do for the very reason that data sources for dropdown values cannot be filtered. There is one workaround but it's pretty ugly because it involves modifying your main data source and polluting your XML. Here is how it would work: Suppose your current data source ...

When you invoke Forms Server, it is usually done via a URL: http://serverpath/_layouts/FormServer.aspx?XsnLocation=...&SaveLocation=...&Source=... Inspecting these values is probably your best bet. Try to see if adding a reference to System.Web.dll in your business logic and getting the value of HttpContext.Current.Request.Url.Query gets ...

The avg() built-in InfoPath function takes a nodeset as an argument, that is, an xpath that evaluates to one or more nodes.For example, if you have a repeating value /my:myFields/my:group1/my:group2/field1 (where group2 is repeating) then a xdMath:Avg(/my:myFields/my:group1/my:group2/field1) will return the average of values of each instance of ...

Since I don't have a repro of this issue I cannot say much but my hunch is that once you get into that "locked" state there is no way back - you'll need to find out how not to get into it. For example, if inserting a row is failing, try to do it via ExecuteAction instead of going via the navigators. It will really have to be ...

Note: I believe you can install TabletPC SDK on a non-tablet machine which would enable some TabletPC features. Check it out here: http://www.microsoft.com/downloads/details.aspx?FamilyId=B46D4B83-A821-40BC-AA85-C9EE3D6E9699&displaylang=en Maybe this will help to reproduce the problem on the dev machine as well

This looks like a timing issue that only reproduces on slow machines. Since this is most likely a bug in InfoPath your best bet is to look for workarounds. One thing you could do is to add Thread.Sleep() calls around your code to see if this makes the problem reproduce on the dev machine (or maybe makes it go away). I believe InfoPath has ...

My guess is that you are hitting a bug in InfoPath itself - not necessarily something you're doing wrong. What would be really helpful is if you could create a simple reproduction of your issue. Could you please create a bare-bones winForms application with a super-simple form and some code that causes the crash?