Hmmm.. Figured something aggravating out. RIAudit, out of necessity, uses public properties, instead of accessors. If i change public string Status; to public string Status {get; set;} then WPF is happy (though the object-ralational database i use is not). I guess I'll have write a wrapper for RIAudit, unless someone knows how to get around this. ??

Hmmm, you'd probably have to do some math to get it to display in the proper format... not sure you can do that with StringFormat, now that I think about it. I'd stick with IValueConverter. [Forum Guidelines]

I couldn't reproduce this error. I have created a native DLL which has a sample NativeDocument class. Exported the functions and used this class from C++/CLI. Created a C# application and referred C++/CLI DLL there and everything worked as expected. If you can provide more information to reproduce, I will try. Best wishes, Navaneeth

When i have int i = 10; i = 5 * i; it knows i'm not trying to multiply 5 * i, but rather 5* the value stored in i. So i'm not trying to cast to a variable (_DataType), but rather the value stored in that variable (int, float, string)... How would generics come into play?

No problem. The need to optimize rises from a bad design. My articles[^]

You can't get the variable name from the object, as you are not accessing the variable. You are just accessing an object that the variable happens to be referencing. There is no backwards reference from the object to the variable. If you want the DataItem object to know the name of the variable, you have to store the name in the object. Despite everything, the person most likely to be fooling you next is yourself.

Thank you very much. Never would have got that on my own. But on some servers the description table is empty, and i'm not getting any return rows. How can i make it optional, to say Return row for key='123' and add the descriptions IF they exist in the descriptions table?

Variables can not be virtual. What you are doing is not overriding, it's shadowing. To tell the compiler that you intend to shadow the variable in the parent class, you use the new keyword: public class Base { public string _Caption="parentresult"; } public class Child : Base { public new string _Caption="childresult"; } If you want to override something, it has to be a property or a method. Despite everything, the person most likely to be fooling you next is yourself.