I like the idea of VB.NET, but from my experiences it seems like a big mess and you have to find a work around to things that should be relatively simple (at least they seem to be).
For our final exam we actually had a take home project. This is a client/server app. that has the client send an XML request to the server, where it is validated for proper formatting, then, if the request is valid (and there is enough of the part they want to order on hand) the server updates its database, sends an XML purchase invoice back to the client, where the client updates its inventory database. The databases are MDBs.
First of all, it doesn't seem like VB.NET has a proper implementation of SQL in it. You can do SQL statements through strings, but not everything works as planned all the time. Quite a headache on occasion. Since we're using Access, I don't know if it's specifically the implementation of SQL, something quirky about VB.NET or something quirky in the MDB files themselves.
I'm glad I took this class though. We have learned some pretty cool stuff, but i've also learned that, if given the choice, I won't be doing VB.NET for a living. [smile].