DavJes wrote: Please just guide me to learn how to do DB design and webservice architecture Can't give more pointers on webservices than the book I mentioned. I've listed some resources on database-normalization, which would be the preferred design IMHO. MSDN[^], explains up to rule #6 MSDN[^], tips Wikipedia[^], with examples and explanation. (Links halfway details on every step) SqlMag[^] has a nice introduction on the topic, as well as a link that explains when normalization should be skipped. Personally, I don't go all the way, just upto BCNF. It's boring and tedious stuff to learn and apply, but I wouldn't recommend it if the advantages don't outweigh the disadvantages; the result will be more confidence in the model used, fewer design-errors, and within a few tables you'll be normalizing your structures without effort. The reason I recommended Mannings' SOA patterns[^] is because it focuses on the most-used patterns; a pattern is a proven and reusable solution, and that's always a nice thing to have in any architecture. I also recommend it because I read and enjoyed it myself :) Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]

Xmal Part missed : ..

Gosh, thanks. Coming from you Dan, that means a heck of a lot. BTW - I've got my preorder in for WP7 Unleashed. I'm not a stalker, I just know things. Oh by the way, you're out of milk. Forgive your enemies - it messes with their heads My blog | My articles | MoXAML PowerToys | Onyx

Not everything is "ready for use" at one point. Some stuff is ready by the time you get to the constructor, some stuff not til the WindowLoaded event, other stuff is not ready til OnApplyTemplate, etc. You have to be more specific.

You repeatedly use the term 'refer', but didn't really clarify at which point you have trouble making the connection between your application and the DLL - it could be at compile time, at linking time, or at run time: 1. compiling Any parts of the DLL that you are supposed to use from outside have to be declared in header files, using the 'extern' keyword. These header files then have to be included in the application that wants to use the DLL. This is neccessary for the compiler to understand the format of the function calls and the types of the parameters and return values. 2. linking Once your application is successfully compiled, the linker will try to resolve the function calls into the DLL. This requires information about the already compiled DLL, which is contained in a file called '.lib'. You have to specify this Lib file (and possibly it's path) in the linker options. With the help of this Lib file, the linker will look up the offset of the function within the DLL and encode this into the function call. 3. running At run-time your application will eventually call the LoadLibrary function that you specified. Provided the DLL can be found at the same location as your application is, or else, if you provided a path, at that path's location, the DLL will now be loaded into memory. When your code runs into a DLL function call, the system will use the linker-provided offset to invoke the correct function within the DLL.

DavJes wrote: So in this case in my client app how do i refer the .h file The same way as any header file is referenced; either add it to your project or add the location to the list of include directories. If you are saying that you do not have access to the header file, then you have a problem. I must get a clever new signature for 2011.

You shouldn't be trying to edit the combo boxes directly, especially if they're in a DataTemplate. Instead, go to whatever they're bound to, and set THAT to null. If your binding is correct, the combos will automatically update themselves. Remember that either the bound object needs to implement INotifyPropertyChanged, or the bound property has to be a DependencyProperty... Otherwise the binding won't be triggered. Proud to have finally moved to the A-Ark. Which one are you in? Author of the Guardians Saga (Sci-Fi/Fantasy novels)

Here you go

Per your title, if this is a COM Server, then you already have access to that in .NET. Just open your .NET Project, right-click on References and select "Add references ...", click on the COM tab and find your COM server in the list of named objects. When you select it, Studio will automatically generate a .NET wrapper to your COM interfaces and you can use that code directly in your .NET project. If it's not already a COM object, you can do it either way: create a DLL that you call into from your .NET project or a COM object that you reference in your .NET Project (as I just mentioned). Not entirely certain this answers your question, if not, you'll need to provide more details as to what, exactly, you're wanting to accomplish. :..::. Douglas H. Troy ::.. Bad Astronomy |VCF|wxWidgets|WTL

Try this article[^] led mike