PlausiblyDamp

Not sure what you mean - if it's contained within System.DLL why would you expect to find it as an extra DLL. Will check later though when I'm near a machine with .Net on it.

Saved = TRUE means you are telling the sheet it has been saved and therefore doesn't need to prompt the user.

You will need to make sure it is added as a reference to the project.

Dim SqlUpdateCommand As New System.Data.SqlClient.SqlCommand or add Imports System.Data.SqlClient to the top of the code module.

The only way to get the correct total is to recursively loop through all the sub folders and count the files in them.

Or all the calls into the compatability layer - overhead for no reason. Or all the Database code still being ADO.

Was never that safe to store them direct in the EXE in older versions of VB (or in an EXE from any language) without doing something to hide them. Also it is a lot more secure to store a hash of the password rather than an encrypted version - with encryption there is always a small chance it could be recovered.

No bug - it's as the error says you don't have a licence to use the control at design time. The control shipped as part of VB6 - you will need VB6 installed on the same machine as your VS.Net ide to get it to work. Also you may need to check the EULA to see if you are legally allowed to redistribute the control depending on how you aquire your copy of VB6.

Puts a line under what? .Length, .Split? if so what error do you get if you move your mouse over the blue line?

What is the desktop OS? Are the machines part of a Domain? IF so the ability to change the system time isn't granted to ordinary users anyway.

You don't need to declare the control WithEvents to use the AddHandler / RemoveHandler commands.

You could make the subroutine accept the form as a parameter, or make the subroutine a public member of the form itself.

You will also need VB6 installed to get the customer controls on your system so the wizard can upgrade code that references them. Probably better of just re-writting the code in VB.Net - the wizard generates bad code with lots of VB6 calls and a compatability layer thrown in as well. Trust me - it will probably be easier and better to write it again.

What errors does it give? There is a migration wizard in 2003 (not sure if it's in all versions though). Although it's an improvement over the one in 2002 it's still pretty naff and I would recomend against using it.

The .OCX will need to be installed and registered on the other machine. It's one of the problems using COM components.

Probably best going with VolteFace's suggestion of putting it in an array and sorting that. As an aside - if you post a question in the Windows Forms forum people are going to assume the question is about Windows Forms.

If the data in the first post is correct tstrings like 'Todd 33 94' are only 11 characters long, trying to do a substring from position 12 within that string will be past the end of the string - exactly like the error says. When you say the split thing doesn't work - what happens? Do you get any results or just an error. Also you may want to try the .Net equivilent of Split Dim Grades() As String 'Set your strStudent this way: strStudent = strStudent.Trim() 'Then get your grades: Grades() = strStudent.Split(" ") 'The students name is now in Grades(0), 'The first grade is in Grade(1), 'The second grade is in Grade(2), 'And if there were more grades just expand! 'For your average: varAverage = (Convert.ToDouble(Grades(1)) + Convert.ToDouble(Grades(2))) / 2

easiest way is put a Console.WriteLine() at the end - app will pause till enter is pressed.

The parameter 'sender' that is passed into the subroutine will be the control causing the Validating event to fire, you can cast this to the correct control type and use it within the sub. Private Sub TextBox_Validating(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles TextBox1.Validating, TextBox2.Validating dim t as TextBox t = DirectCast(sender, TextBox) 't.Name should be the correct textbox name. End Sub

firstly just attach code - not .exe files (even in a zip) - an admin will probably delete the attachement if it contains executables. Not sure why it's doing it but if in the frmMain_Load event replace the line newTransportRecord.WindowState = FormWindowState.Maximized with something similar to newTransportRecord.Height = Me.ClientSize.Height - Me.PictureBox1.Height - Me.MainToolBar.Height newTransportRecord.Width = Me.ClientSize.Width newTransportRecord.Location = New Point(0, Me.PictureBox1.Height) you may have to juggle the numbers a bit to get it to fit. Must ask though - why are you removing the control box etc. I find it really off putting to not have them there in a windows app. Also would you not be able to acheive the same end result using panels or something similar?

You could include the call to .ExecuteScalar within a Try / Catch block.

What is the contents of the string you are passing in?

I just tried creating a simple application. Created a MDIContainer and set it's ControlBox, Minimaze and Maximize buttons to false. Added a child and set same as above. Got the MDI container to create a child form and maximize it and neither had Controlbox, Minimize or Maximize buttons showing, so not sure why your's is behaving any differently. Do you have any other code that refers to these properties?

It can be used with local accounts. IIRC you can use the same WINNT://name,computer syntax

If you set the child form to not show the Minimize, Maximize and control box items then the child won't. The parent will as you've not told the parent not to display them.