I have roof estimating software and am having a problem on one computer.
I think the machine may not have the right version of vb runtime files.
Will running VBRun60sp6.exe overwrite the the incorrect runtimes with the correct ones?
Printable View
I have roof estimating software and am having a problem on one computer.
I think the machine may not have the right version of vb runtime files.
Will running VBRun60sp6.exe overwrite the the incorrect runtimes with the correct ones?
What is the problem?
Is there anything obviously different about that computer? (eg: does that one have Windows Vista, but none of the others do?)
With the information you have given so far, there is no way to limit it to anything.
Thanks for your replyQuote:
Originally Posted by si_the_geek
It's an xp machine. My installer does not overwrite any files, if they are already present and it installs 3rd party Ocx's and dll's. The error occurs when he tries to save a file. It works fine on his desktop, but not his laptop. I have searched thru the file save routine to no avail. My reason for this post is to make sure he has the correct vb runtimes as a starting point. My installer includes the vbruntimes but does not install them if they are present
Ps
I am waiting for my hair to grow back from the last time I tried to install to Vista
If it doesnt save on his laptp then what is the error message? It could just be as simple as a permissions issue on his laptop if its not on the domain for example.
RUN-TIME ERRE 380 INVALID PROPERTY VALUEQuote:
Originally Posted by RobDog888
Its not polite to type in all caps as that means you are yelling, I'm sure you know this.
I just copied and pasted his email, didn't think about it. I guess he was yelling at me. SorryQuote:
Originally Posted by RobDog888
I'm fairly sure that error can be caused by many different things.. can you show us the code for that routine? (and preferably tell us which line it occurs on, but I'm guessing you don't know that)
The file save routine just has too many lines of code and subroutines to post.Quote:
Originally Posted by si_the_geek
I am going to send the customer a exe with check points in the file save routine.
Like this Msgbox " Check point 1" etc and see if i can narrow it down to a specific line, subroutine or function
There is no need for that long-winded process - you can find out the exact line by adding ERL to your error handler, eg:
Unfortunately you also need to write numbers on every line of code in the routine, but if you have MZTools (free, link in my signature) it can do it for you automatically - just press a button to number all lines in the routine/form/project.Code:ErrorHandler:
MsgBox "Error " & Err.Number & ": " & Err.Description & vbNewLine _
& "on line " & ERL
My error hander is written like this:(Referenced in about 500 places)Quote:
Originally Posted by si_the_geek
e:
MsgBox "file save " & err.number & " " & err.Description
But its not getting to the error handler
I am starting to think maybe a subroutine or function does not have error handling i will have to check. I do have MZTools, didn't know you could use it that way. I have put 16 breakpoints compiled and sent it to my customer.Code:Public Sub ErrHandler(loc As String, Num As String, dscr As String)
MsgBox "There was an Error" & vbCrLf & vbCrLf & _
"Error Location " & loc & vbCrLf & _
"Error Number " & Num & vbCrLf & _
"Description " & dscr & vbCrLf, vbOKOnly, "Warning - Error"
End Sub
I will be back
Thank you
Never mindQuote:
Originally Posted by si_the_geek
I changed the order of items being loaded in a form load and fixed the problem
Just goes to show the least tweak can create or fix a problem. Remains a mystery why just 1 computer
Code:Call FormSize 'moved to here 08-01-08 setformsize based on resolutation
Call LoadGrids 'moved to here 08-01-08 fill the 5 flexgrids from file
Call PositionGridLabels 'Position label and other layout
'Call LoadGrids 'moved from here 08-01-08
'Call FormSize 'moved from here 08-01-08
I would guess that the size calculations (or default positions) that are used in LoadGrids or PositionGridLabels are not valid due to the particular resolution on that computer - so you were probably trying to do something like set the width of a control to a negative number.
I think you hit the nail on the head. The form in question saves it's position to an .ini file. Have not checked yet but I hope i wrote code to check for form being minimizedQuote:
Originally Posted by si_the_geek
Yea, if you save the minomized coordinates then they will all be negative numbers and cause your error.
I fixed that form by taking off the minimize button as there is no reason to allow it to be minimized. Also wrote code to check for negitave numbers as a save guardQuote:
Originally Posted by RobDog888
Cool, so everything is working now?
Ps, GO Raiders FTW!!! :thumb:
Yep, my customer is probably whistling right now.Quote:
Originally Posted by RobDog888
PS after this year I'm changing my signature to have a smiley next to Raiders