Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
I'm sorry, but rather than you wasting your time waiting for an answer here, I'd suggest that you aren't going to get an answer here. Your best bet for an answer on this would be to search the support forums on SAP, and to try searching through Google.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
Difficult to say without more info.
You'd probably need to get the info from SAP somehow (with the SAPdotnetconnector3.0 I assume), but you should check the documentation and/or sample code of that tool for more info. It could push the info or it could pull the info.
If you finally receive the info you can build "object classes" of the info you received and bind the properties of those classes (which you put in collections) to the grid.
You'll need to be more specific and give more specific problems if you want an answer. If I would answer this one best I could I'd need to research several hours or longer and write quite a lot of text.
Have a look at the XmlDocument class here[^].
Basically you'd create a XmlDocument object and add XmlElement [^] instances.
XmlDocument document = new XmlDocument();
// Create the root Account element.
XmlElement root = document.CreateElement("Account");
// Add attributes to the element
// Add the element to the document's tree.
// Create the child elements
XmlElement child = document.CreateElement("User1");
// Add the child to the root element
// Create a grandchild
XmlELement grandchild = document.CreateElement("AccountSetting");
//etc, etc...//Finally you could save the document to file:
Clear in my head, even the syntax with the colon and the type before the opening bracket.
Thanks for the pointer to the syntax page. I thought "UniqueValue" was a keyword or something, stuck it into the search thing on msdn and came up with zero; at which time I had a major DUH moment. Your suggestion clarified a lot for me. Thanks a ton.
Hold it, wait a minute, on that msdn page, I just read this...
From the MSDN page:
Usually it is best to define an enum directly within a namespace so that all classes in the namespace can access it with equal convenience. However, an enum can also be nested within a class or struct.
I thought that every variable had to be in a class; but then these aren't variables; I guess; somebody fix my brain on this matter.
So then, if I take the enum thing (what is the right word for "thing" in this context ?) out of the class structure, and just put it after the opening bracket of the namespace, I can use the names in the enum list as they are ? Without the UniqueValue.Fred nomenclature ?
e.g., I could just use the name "Fred" (no quotes" and get a guaranteed unique value ?