You need to append the top level node to the m_pXMLDoc->documentElement.

IMO, after signalling the thread to stop you should use WaitForSingleObject.

A void* doesn't have a NextObject method. You would need to cast this to the appropriate object with something like Room* tmpRoom = reinterpret_cast(Node) tmpRoom will be null if the cast fails.

ATL has a version of CString in atlstr.h. You should be able to use this.

See this

I think you are trying to allocate over 2GB of space.

IMHO, the common quality to all really good developers is problem solving skills. This quality separates those that do great things in the technology industry and those that are always worried about layoffs. I see two problems here that you need to solve. The first is the encrypt/decrypt functionality, which the professor has already given the solution. The other problem is how to use pointers. Is there something more specific you would like to ask?

Using OLEDB Attributes is no different than using OLEDB Consumer templates. There are a number of examples on using the OLEDB templates at http://www.codeproject.com/database/#OLE+DB

Only 1 db_command is required using a SELECT statement. If you add DBPROPVAL_UP_CHANGE | DBPROPVAL_UP_INSERT | DBPROPVAL_UP_DELETE to the DBPROP_UPDATABILITY property, the rowset will allow INSERT, UPDATE, and DELETE through it's member functions.

You have a point but I have yet to hear any group, government, or other interests say that they will not allow Microsoft to do business in their area. IMO, Microsoft is at the top for a good reason: because no other company has produced such well accepted software. This is not to say that it is the best software there is but at the very least Microsoft has been much more successful on the marketing front.

I guess it depends on what you're trying to do. Lately I have been working with XML out of databases and find that ADO.NET has much more functionality in that area. If your app is not using the .Net platform then it will probably be too much overhead to include with the distribution.

Do you mean something like select name, code from [TABLE] group by code, name

IMO, the benefits of ADO far outweigh that of DAO (ADO.NET is even better). With MS declaring DAO depricated in VC7, this not only means no support but also no backward compatibility. MSDE is more robust and has much more functionality than Access. Users can continue to use Access by linking to SQL Server.

Let me preface this question with this: I work in a VB shop. We turn to VC++ when performance is a concern or the solution simply cannot be implemented in VB. Since Managed C++ will compile to a common language assembly, the same as C# and VB.net, what would the diffence be other than syntax. Has anyone found any perfomance gains with Managed C++ over C# or VB.net? Other than a programmer's preference to use C++ syntax, why would someone want to use Managed C++?