How do I determine the error?

[bminaeff]

I have a program that I did not write but all of a sudden it is giving a run-time error when we try to load. This program has run for about 7 years without issue. Today I have a run time error "'-2147024882 (8007000e)' System Error &H80004005 (-2147467259). Unspecified error" I added some error handling to the main form and have an err.number = 0 and err.description = "".

This seems to be the sub that gives me an error :

Private Sub Form_Load()
On Error GoTo LoadError

Dim lpSystemTime As SYSTEMTIME
Dim slong As Long
With Me
   .Width = Screen.Width
    .Height = Screen.Height
    Left = 0
    Top = 0
    MainMenu.BorderStyle = (Color = vbRed)
End With
menuframe.BackColor = RGB(250, 175, 0)

slong = GetSystemTime(lpSystemTime)

Print
LoadError:
MsgBox ("Error Number: " & Err.Number & ". Error Desc.: " & Err.Description)

End Sub

How can I determine what is causing this?

 

[HarleyQuinn]

It's your Print statement, the syntax for Print is:

Print [i]#filenumber[/i], [[i]outputlist[/i]]

Hope this helps

HarleyQuinn
---------------------------------
The most overlooked advantage to owning a computer is that if they foul up there's no law against wacking them around a little. - Joe Martin

Get the most out of Tek-Tips, read FAQ222-2244 before posting.

 

[SBerthold]

Form "Print" should work fine this way. Just don't understand why it is being used here.

Looks more like an error with a database connection. Are you using a data control? What is the database? What is the connection string?

 

[HarleyQuinn]

I know why it broke on the Print for me, basically it didn't, I missed that there's no Exit Sub after it so it goes straight to the error handler which is why I got the same behaviour as the OP, there wasn't an error

HarleyQuinn
---------------------------------
The most overlooked advantage to owning a computer is that if they foul up there's no law against wacking them around a little. - Joe Martin

Get the most out of Tek-Tips, read FAQ222-2244 before posting.

 

[SBerthold]

Also, it doesn't look like the complete code for this sub, or you are missing an Exit Sub prior to the LoadError tag. And, you may want to not resize/reposition the form here. Block out all code here and see what happens.

 

[bminaeff]

SBerthold is correct, I forgot the exit sub, so the error is not on this sub.

Basically, this program has been around for 7 years or so running fine everyday. All of a sudden this error has popped up and crashes the program just when it loads. I am not really a vb6 programmer so I am struggling a bit.

Odd thing is it seems to work fine when running the program in debug from the ide, but when we launch the executable it crashes. Any thoughts?

There is a local database (Sql 2000 I think) and 2 winsock connections, but I have no idea if it get here before crashing or not. I am going to work on that today.

 

[strongm]

Are you using any custom controls on the main form?

 

[bminaeff]

Strongm

I dont think so, everything looks pretty standard. I found that the program loads a few forms from a module right in the beginning, so I decided to put message boxes up after each loaded properly to determine where it was failing. It seems that it fails settings up some connection to the PLC that is connected, so now I just have to dig through there. I also found 2 other errors in the program trying to find where this error was so I think I am on the right path and the path just got longer. I wont bore you guys with that code but thanks alot for all the help.

Anyway, would anyone know why it would work fine when running it from visual studio but fail on the executable? Just curious.

Again Thanks
-Bill M,

 

[Andrzejek]

In your VB IDE, go to Tools - Options.... - General Tab.

You have a Frame called: Error Trapping with 3 options:
o Breal on All Errors
o Break in Class Module
o Break on Unhandled Errors

I would try to run your code with first option chosen. It will ignore all error trapping and stop on any error in your code.

Have fun.

---- Andy

 

[SBerthold]

As I said, it looks more like an error with a database connection. That is just a thought though, but it could be anything other.

Anyways, test the connection and use a message box to show the results.