Try Catch and Finally, yes make use of the Finally!

The "Finally" in the Try Catch statement is a great place to close your connection.

Public Sub TestFunction()
Try
Return
Catch ex As Exception
Finally
Console.WriteLine("TestFunction finally called!")
Throw New Exception("Error!")
End Try
End Sub

regards,
choongseng

Remote Desktop Administration

Very annoying warning message like this every time you connect to a non-vista Windows Box?

Here's the solution (permenant):
At registry section HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client,
add a DWORD (32-bit) Value, name AuthenticationLevelOverride with value 0.

Taken from:
http://blogs.vertigo.com/personal/steventap/Blog/Lists/Posts/Post.aspx?ID=3

A more Official solution w/o changing the registry is:
http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-connection-authentication-faq.aspx#_Prompted_for_Authentication

In the same page above also explained why sometimes when you connect to a windows box, it prompts the authentication box for user login again.





regards,
choongseng

db4o - Open Source Object Database

db4o - Open Source Object Database
http://www.db4o.com

Got heard of this from Johnson, and it looks promising from the site's reviews and comments.

It supports 3 type of query methods:
1) Query-By-Example
2) Native Query
3) SODA Query API

It looks pretty good, until I read this on the CascadeOnDelete:
"Houston, we have a problem - and there's no simple solution at hand. Currently db4o does not check whether objects to be deleted are referenced anywhere else, so please be very careful when using this feature."

However, as long as you don't make use of this Cascading feature, you are safe from hassle of debugging your apps for some unexpected behavior.

Running out of time and I've used this to built my prototype web apps and it indeed save me lots of time writing SQLs, guess I'll be using it until my data structure and my DAL is out.

regards,
choongseng

No Remote Connect Console on Windows 2000 box

Was hunting up and down why I didn't manage to connect to Win2k servers to its console session. Too bad, no luck for that though:

You cannot use Mstsc.exe with the /CONSOLE switch to connect to a console session on a Windows 2000 Server-based computer
http://support.microsoft.com/kb/311926

Remotely Administering Windows Servers
http://www.windowsnetworking.com/articles_tutorials/Remotely-Administering-Windows-Servers.html

regards,
choongseng