Visual Basic

I'm not sure if it's what you want, but maybe the GetSetting and SaveSetting functions are useful? they save info in the registry - very useful for options dialogs etc. Hope it helps Paul W -- A wise fox has many exits from its burrow.

To make a Connection using this is simple. Using "Option Strict": Dim sqlCon As SQLClient.SQLConnection = Ctype(DataSource.Connection, SQLClient.SQLConnection) Not using Option Strict: Dim sqlCon As SQLClient.SQLConnection = DataSource.Connection Even if you don't explicitly call "DataSource.Connect", the DataSource class knows it needs to make a Connection.

thanks, good to know. norm

Nick Parker wrote: however there are many things as I am learning that can be done in C++ that just can't be done in VB. Absolutely. I have to write my own linked list because VB does not provide one. How is that remotely a programming language ? But as I said, if I had started it, I would have done it in C++. We still haven't figured out how to debug our dll. And the syntax is just crap. There are so many examples of design with no thought for the consequences, it's really quite frustrating. Christian No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002 C# will attract all comers, where VB is for IT Journalists and managers - Michael P Butler 05-12-2002 Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002

I am writing a VISUAL BASIC(VB.NET) application that will utilize the ASP.NET cache. See your second quote !!

You need to download the latest version of MDAC[^]. Paul van der Walt wrote: Or maybe one of you has another solution? Use a decent DBMS like SQL Server, or, if you can't afford it, use MSDE. I see dumb people

Daniel Turini wrote: Nil, Nada, Nothing, Nyet, Niente. So are you saying there isn't any. :laugh: ;P Nick Parker Not everything that can be counted counts, and not everything that counts can be counted. - Albert Einstein

Try http://www.codeproject.com/useritems/Using_PropertyGrid.asp

Thaks dear, The same thing I did just two days ago myself. You are a little late but it is good that at least you are. ;P Again, Very very thanks to you, Sameers

This is very simple. You shout not Dim a NEW instance of your Form1 because it should already open. Instead call the controls on the already open Form: Form1.MenuItem1.Enabled = True

But in fact,I see such dim : dim form1 as form2(form2 is an user-defined class) and the app uses "form1.param1"(param1 is also defined in class form2) immediately,not use new pointer first. this is my signature for forums quoted from shog*9: I can't help but feel, somewhere deep within that withered, bitter, scheming person, there is a small child, frightened, looking a way out.

Setting an Object = Nothing does not ALWAYS free the memory in VB6 (this goes for .NET as well). Get familiar with the Objects you are using, if they implement a "Close" or "Dispose" method, ALWAYS use it before Setting your Object = Nothing. For example, watch ADO eat up memory in a VB6 app. However, when you use the Close method, the memory usage goes way down. It takes a little while for the VB6 runtime to clean up the memory references, but it happens.

Try this: ControlPaint.DrawImageDisabled(Graphics, Image, x, y, BackColor)