Sorry Confused already delete fronm there

I've never got along with Events - they seem overly convoluted for simple tasks. My (also) rusty VB suggests that something like the following might do what you want (it is probably overkill) Public Class Form1 Private f2 As Form2 = Nothing Sub F2IsActive(Enabled As Boolean) btnStartForm2.Enabled = Not Enabled btnDoSomethingOnForm2.Enabled = Enabled btnCloseForm2.Enabled = Enabled If Enabled Then If Not FormIsOpen(f2) Then ' Needs to be opened f2 = New Form2() f2.Show() End If ElseIf FormIsOpen(f2) Then ' Needs to be closed f2.Close() f2 = Nothing End If End Sub Private Sub btnStartForm2\_Click(sender As Object, e As EventArgs) Handles btnStartForm2.Click F2IsActive(True) End Sub Private Sub btnDoSomethingOnForm2\_Click(sender As Object, e As EventArgs) Handles btnDoSomethingOnForm2.Click If f2 Is Nothing Then MsgBox("You have to open Form2 first") ElseIf FormIsOpen(f2) Then f2.DoSomethingOnForm2() Else ' No longer exists MsgBox("Form2 has disappeared") F2IsActive(False) End If End Sub Private Function FormIsOpen(formToFind As Form) As Boolean For Each testform As Form In Application.OpenForms If testform.Equals(formToFind) Then Return True End If Next Return False End Function Private Sub btnCloseForm2\_Click(sender As Object, e As EventArgs) Handles btnCloseForm2.Click If Not FormIsOpen(f2) Then MsgBox("Form2 has already been closed") End If F2IsActive(False) End Sub Private Sub Form1\_Load(sender As Object, e As EventArgs) Handles MyBase.Load F2IsActive(False) End Sub End Class Public Class Form2 Public Sub DoSomethingOnForm2() MsgBox("Hello from Form 1") End Sub End Class

How about this approach ... 1) Run the process as a test, collecting the total time it takes. Call it "T" 2) Store that run time somewhere 3) Next time you run the process you can now use "T" as the denominator to calculate the percent complete. p = duration_now/T 4) If the percentage calculation goes over 100, then set it 100. 5) Capture the new total time, "T", store it for the next iteration. Rinse, repeat. Not perfect, but it might work for you. :java:

thanks clear

An int16 (or 'short') is a two-byte value. Intel processors are "little-endian", meaning the last byte (least significant) is stored first and the first byte (most significant) is stored last. In your example, your two byte value, (12) 0x000C, is stored in memory like this: 0x0C, 0x00. So that's why you're getting the bytes in the order you are. BitConverter is returning the bytes in the order they appear in memory. If you were running the exact same code on a processor that is big-endian, the bytes would show up in the array in the order opposite of what you're seeing now. Now, having said all that, if you're looking for just getting a string for the hexadecimal representation of your value, all you have to do is this: Dim myInt As Int16 = 12 result = String.Format("X", myInt) If you're dealing with values that will never be greater than 255, why are you using an Int16? Why not just use Byte instead? Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak

Your code is vulnerable to SQL Injection[^]. NEVER use string concatenation to build a SQL query. ALWAYS use a parameterized query. Everything you wanted to know about SQL injection (but were afraid to ask) | Troy Hunt[^] How can I explain SQL injection without technical jargon? | Information Security Stack Exchange[^] Query Parameterization Cheat Sheet | OWASP[^] "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

I suggest you dig more in Hierarchical term. This is an example of visual basic .net winform project that uses MS-Access 2007 database and populate a TreeView control with all Data as [Parent->Child->GrandChild]. VB.NET Access 2007 Hierarchical TreeView[^]