Steve,
You might let those who aren't using the right version know through your
script, rather than have it throw errors. As Alan innocently
demonstrated, errors tend to create unnecessary support problems,
whereas simple messages do their intended job of informing.
The Framework script does this with a simple:
If InStr(CStr(Version), "7.0") <> 1 Then
' Do fun stuff
Else
' Tell them they need a better Window-Eyes
End If
This says, if they're running anything that starts with a "7.0" in the
version number, tell them they're out of luck.
This will account for future versions as well, so that you don't have to
keep version checking unless you take advantage of additional future
features.
If they are running an older version, and they did accidentally install
the latest, when you tell them they're out of luck, you might also give
them a button that takes them to the script's website where they can
download older versions. That's all up to you -- just a thought.
Aaron
On 6/9/2009 8:35 PM, Stephen Clower wrote:
Click the "Read More" link on the Voice Rotor page. You will see every
version that has been posted to SC. Choose 1.09, and you will be good to
go.
Regards,
Steve
On 6/9/2009 8:30 PM, Alan R. Downing wrote:
Ok, how do I get the older version back???
----- Original Message ----- From: "Stephen Clower"
<[email protected]>
To: <[email protected]>
Sent: Tuesday, June 09, 2009 5:28 PM
Subject: Re: Voice rotor update issue
You need Window-Eyes 7.1 or later to use the new version of the script.
Regards,
Steve
On 6/9/2009 8:04 PM, Alan R. Downing wrote:
It also says Microsoft runtime error line 14 column 14 mismatched menu.
That is a slight paraphrase, but close.
----- Original Message ----- From: "Aaron Smith" <[email protected]>
To: <[email protected]>
Sent: Tuesday, June 09, 2009 4:56 PM
Subject: Re: Voice rotor update issue
Alan,
Can you provide the exact error message you're getting?
Aaron
On 6/9/2009 7:41 PM, Alan R. Downing wrote:
I elected to install the published voice rotor update but I got
the you
are about to replace a newer script with an older one. I proceeded
anyway, and then got a run-time error of some sort.
Anyone else seeing this?
Alan R. Downing
Phoenix, AZ
KD7GC
--
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
--
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
