Since neither the Form nor the Form's Controls collection is Serializable, you'll have to implement some kind of collection yourself. Serializing the entire form is just overkill if all you're doing is changing the text of a few labels. First, what are the properties you're allowing the user to change? Are you also allowing the user to add/remove the number of controls? What types of controls? Are the properties you're allowing change to common between all of them? Once you have all these questions answered, you can create a class and collection manager to hold this information. This is where you can add your own serialization support. Google for "custom collections vb.net" for examples. Dave Kreskowiak Microsoft MVP - Visual Basic

I agree with CWIZO. There's NEVER a reason to tie data directly to the names of objects in your code. This reeks of a bad design waiting to explode in your face. Dave Kreskowiak Microsoft MVP - Visual Basic

You have 2 choices: select case FormToDisplay case "Form1" dim form as new Form1 case "Form2" dim form as new From2 case "Form3" dim form as new Form3 end case form.Show or Look at using reflection. Mike Lasseter

What does this have to do with VB.NET?? :confused: RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

The short answer is No. The long answer is Maybe, but you'll need resource hacking tools to find out. If the image is in a resource inside the executable, then you MIGHT be able to replace it without breaking anything. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

You should enable visual styles in a Main function, before your form gets loaded, then call DoEvents(). I recommend that you create a Main class and add the Main method there as shown below. Public Class Main Public Shared Sub Main(ByVal args() As String) Application.EnableVisualStyles() Application.DoEvents() Application.Run(New MyForm) End Sub End Class Next, you need to change your project setting's Startup Object to "Sub Main". You can find this option by right clicking your project in the solution explorer, click on Properties, select CommonProperties\General in the dialog's tree.

This is a bug in the .NET framework. You can work-around it by calling Application.DoEvents() after EnableVisualStyles.

You can start by reading up on the PDF file format specification[^] ColinMackay.net Scottish Developers are looking for speakers for user group sessions over the next few months. Do you want to know more?

just to clarify, the Application.EnableVisualStyles() should go in the program's Main() method