B
Bob Phillips
We recently announced the release of CFPlus, an extended conditional
formatting add-in .
A number of users with older operating systems, such as Win95 and WinME,
have reported receiving an Error 5 on loading the add-in. We believe that we
have found the cause of this error and fixed it, so you should be able to
get the fixed version at the same place,
www.xldynamic.com/source/xld.CFPlus.Download.html.
We would be grateful to hear from anyone who suffered this error as to
whether it is now cured for them, quoting the OS and Excel version please.
For anyone who is interested, the problem was caused by a call to the
GetPrivateProfileInt API. The code was issuing this call, and then calling
GetPrivateProfileString if that call failed (as we are catering for numeric
and string values). We had one key value of 'x10', which we wanted to be
returned as a string. In NT/Windows 2000/XP, this is exactly what happened.
However, in the other systems, the 'x10' is read as a hexadecimal number
(value 16 in this case), and so the code failed on the expectation of a
subsequent string key that wasn't there.
Frank Kabel & Bob Phillips
formatting add-in .
A number of users with older operating systems, such as Win95 and WinME,
have reported receiving an Error 5 on loading the add-in. We believe that we
have found the cause of this error and fixed it, so you should be able to
get the fixed version at the same place,
www.xldynamic.com/source/xld.CFPlus.Download.html.
We would be grateful to hear from anyone who suffered this error as to
whether it is now cured for them, quoting the OS and Excel version please.
For anyone who is interested, the problem was caused by a call to the
GetPrivateProfileInt API. The code was issuing this call, and then calling
GetPrivateProfileString if that call failed (as we are catering for numeric
and string values). We had one key value of 'x10', which we wanted to be
returned as a string. In NT/Windows 2000/XP, this is exactly what happened.
However, in the other systems, the 'x10' is read as a hexadecimal number
(value 16 in this case), and so the code failed on the expectation of a
subsequent string key that wasn't there.
Frank Kabel & Bob Phillips