-
A GUID is easily generated from managed code (C# / VB.NET):
string uniqueId = System.Guid.NewGuid().ToString("N");
the "N" portion tells it to leave out all the dashes. If you want those, just use .ToString() instead.
-
Ah! I'm glad you caught that one. I had intended to mention it in my last posting but forgot to because I started getting into all those other things. Disable/EnableAutoUpdate are essential when copying data into the Main DOM. They can make all the difference in the world so far as performance. But they, as mentioned, are not the only issues. ...
-
Unfortunately, browser forms are not up-to-par with the fat-client forms. There are numerous reasons why a browser form will slow down--way beyond the scope of any reasonable conversation... but having too many controls in the view is one of those reasons. How many is too many? Again, hard to say.
Certain things in browser forms do not occur ...
-
What is the error you are getting? When does it occur? It could be that you are failing to update SQL because there are some required fields (red asterisk) that aren't filled in or because there are some field with invalid data (like a date picker with a text value -- red dashed border).
AND, if not all nodes are represented by fields are in ...
-
InfoPath has many performance related issues, especially when you start talking about very large query results and large DOM transfers (most especially to the Main DOM).
Every time you make a modification in the Main DOM, any associated rules and code will run. So for each cloned node you insert, your background logic runs.
Views start slowing ...
-
Did you try setting the margin and padding values all to zero and make sure there was no 1pt white border on the section?
-
The problem with attempting to use the ID value is that it is not assigned until AFTER the form has been saved to SharePoint. As you want to assign it when the form is first created, this will be of no use to you.
The posting you refer to looks interesting, though I get nervous when I see the term "unsafe" thrown around in ...
-
Right-click your text box and choose Properties.
On the Display tab, select the Wrap Text check box.
In the Scrolling drop-down, select Expand To Show All Text.
Now your users will see everything they typed in. The text box will expand vertically to show all lines of text.
-
The traditional approach to this is to use a database to generate the next number. I don't know that SP has any ability to do this on its own.
-
Two choices: 1) set your text box to auto-expand, 2) Create a print view that allows that field to expand as needed.