now press F8 repeatedly and see if it gets past the CheckRelease function.
- Vote on answer
- posted
18 years ago
now press F8 repeatedly and see if it gets past the CheckRelease function.
It goes up to the same offending line CheckRelease = CLng(Left(swApp.RevisionNumber(), InStr(swApp.RevisionNumber(), ".")) and then shows the 'type mismatch error' message as usual.
Now press F8 repeatedly till past the End Function line.
It still stops at the same line
CheckRelease = CLng(Left(swApp.RevisionNumber(), InStr(swApp.RevisionNumber(), "."))
And gives the same error message
Duh, do you see the problem? The first is from your code and the second from mine. Somehow a closing paren went missing. Sorry, I should have caught that long ago.
CheckRelease = CLng(Left(swApp.RevisionNumber(),InStr(swApp.RevisionNumber(), "."))
CheckRelease = CLng(Left(swApp.RevisionNumber(), InStr(swApp.RevisionNumber(), ".")))
No, sorry, that's not it. I probably missed one when copy/pasting around... Here it is correctly copied from the macro editor (and it doesn't have a line break)
CheckRelease = CLng(Left(swApp.RevisionNumber(), InStr(swApp.RevisionNumber(), ".")))
I am about at the end of things to try.
Paste this in:
CheckRelease = 13 'SW 2005
And comment out the offending line with a single quote at the beginning of the line.
Yeah! that works!
Thanks,
-Marc
If you run on 2004 use 12, 2005 use 13 and 2006 use 14.
I am at a loss to know why that line of code is not working for you. It has to be in Instr or Clng.
I did the test on 15 machines here and it's the only one with that problem. There's even one wich was bought and configured at the same time and is, as far as I can tell, identical...
Thanks anyway for your efforts and the time you put on that tool,
-Marc
Which suggests that there might be a problem with VBA that you want to follow up on.
It would be nice to see the results you got too. Especially how much variation you had between machines and what the hardware was.
It's not complete but so far; All were with 5 iterations, rebuild time added and done 3 times. All with SW 2005 Score is this Excel formula: =((45.59+4.47)+(42.75+3.75)+(43.47+4.17))/3
Athlon64 3800+ 2GB RAM XP Pro SP2 = 48.07 Athlon64 3000+ 1GB RAM XP Pro SP1 = 48.97 Athlon64 3800+ 2GB RAM XP Pro SP2 = 54.11 Pentium m 1700 512MB RAM XP Pro SP1 = 59.61 (centrino notebook)
2x Opteron 246 4GB RAM XP Pro SP1 = 81.84 (This one still rocks for renderings but is not very good with SW) AthlonXP 2400+ 1GB RAM XP Pro SP1 = 83.95 AthlonXP 2200+ 1GB RAM XP Pro SP1 = 85.61 Pentium 4 2800 1GB XP Pro SP1 = 108.06 Pentium 4m 1900 512MB XP Pro SP1 = 121.05 AthlonXP 1800+ 1GB RAM WIN2k = 127.57 AthlonXP 2600+ 1GB RAM XP Pro SP1 = 234.87 (My workstation, needs a reformat)We see that some machines needs to be tuned up.
I also do a rendering test with 3dsMax and it's not always the same order...
-Marc
If it is available could you post the averages of both the score for construction and the rebuild separately?
The Opteron score does not make much sense. I have an FX53 which is about as close to Opteron as you can get and it is faster than any of these scores. Can you set processor affinity to a single processor for SW and see what happens?
Here are the full results. I also included the results of a rendering test done with VRay within Max, the score is in percentage of the fastest.
2x Opteron 246 4GB RAM XP Pro SP1 =((74.05+4.6)+(77.42+4.95)+(79.14+5.37))/3 = 81.84 Rendering = 100%I cannot do any tests today as it's rendering full-time for a few days, and I'm going in vacation for two weeks.
The others:
Athlon64 3800+ 2GB RAM XP Pro SP2 =((45.59+4.47)+(42.75+3.75)+(43.47+4.17))/3 = 48.07 Rendering = 58%
Athlon64 3000+ 1GB RAM XP Pro SP1 =((46.16+4.19)+(46.75+4.44)+(40.53+4.84))/3 = 48.97 Rendering = 54%
Athlon64 3800+ 2GB RAM XP Pro SP2 =((49.4+4.87)+(48.65+4.32)+(49.96+5.13))/3 = 54.11 Rendering = 63%
Pentium m 1700 512MB RAM XP Pro SP1 (centrino notebook) =((53.2+5.44)+(53.9+5.66)+(55.6+5.02))/3 = 59.61 Rendering = NA
AthlonXP 2400+ 1GB RAM XP Pro SP1 =((78.52+6.81)+(75.96+6.59)+(76.88+7.09))/3 = 83.95 Rendering = 42%
AthlonXP 2200+ 1GB RAM XP Pro SP1 =((77.07+7.26)+(78.15+7.64)+(79.06+7.65))/3 = 85.61 Rendering = NA
Pentium 4 2800 1GB XP Pro SP1 =((102.1+6.74)+(103.48+7.29)+(97.82+6.74))/3 = 108.06 Rendering = 52%
Pentium 4m 1900 512MB XP Pro SP1 =((113.5+9.47)+(109.68+9.91)+(110.8+9.79))/3 = 121.05 Rendering = NA
AthlonXP 1800+ 1GB RAM WIN2k =((117.15+9.61)+(117.77+9.58)+(119.22+9.39))/3 = 127.57 Rendering = 32%
AthlonXP 2600+ 1GB RAM XP Pro SP1 =((231.54+8.56)+(230.73+8.54)+(217.66+7.59))/3 = 234.87 Rendering = 34%
-Marc
SW2004 gave times a little slower than 2005 when I had an assembly loaded. I unloaded and restarted.
PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.