keymap-master v8.38 available!

jon9 · Post by **jon9** » Mon Jan 16, 2006 6:31 pm

I'm in no hurry at all and much appreiciate any help what so ever. Email me if I can be of any assistance.--john

Mark Pierson · Post by **Mark Pierson** » Mon Jan 16, 2006 6:42 pm

This may be harder than I thought...

Can you do me a favor? Open a blank spreadsheet, select a cell, and try to enter the following function:

=DEC2HEX(1,2)

Does it work (should display "01"), or to your get a #NAME? or some other error?

Also, if you go to Tools, Add-Ins..., does the list contain a reference to Analysis ToolPak?

jon9 · Post by **jon9** » Tue Jan 17, 2006 12:21 am

Does it work (should display "01"), or to your get a #NAME? or some other error?

yes, it displays 01

Also, if you go to Tools, Add-Ins..., does the list contain a reference to Analysis ToolPak

No

Mark Pierson · Post by **Mark Pierson** » Tue Jan 17, 2006 9:45 am

jon9 wrote:yes, it displays 01

Hmmm... now I'm perplexed. If that works but you still get the ToolPak error from KM 8.38beta1, the only thing I can think of is that XL12 doesn't for some reason support the function renaming convention we use in KM. If that's the case, I'm not sure there's an easy workaround.

Try 8.38 beta2 and let me know if you still get the TP error. If so, I may not be able to figure it out until I can actually work with it in an XL12 environment.

jon9 · Post by **jon9** » Tue Jan 17, 2006 10:08 am

I'll try it when I get home this evening.

Post by **The Robman** » Tue Jan 17, 2006 11:09 am

That would be easy to test.

Jon, please try this...

1. Fire up a new clean spreadsheet
2. Go to Insert > Name > Define, this will bring up the "Define Name" pop-up.
3. Under "Names in workbook" enter dec_to_hex
4. Under "Refers to" enter =DEC2HEX
5. Now, go back to the regular spreadsheet and try entering the following formula:

=dec_to_hex(16)

this should give the same result as if you had entered =DEC2HEX(16) (ie, hex value "10")

Mark Pierson · Post by **Mark Pierson** » Tue Jan 17, 2006 2:36 pm

The Robman wrote:That would be easy to test.

Except that this is essentially what KM is already doing. The failure of a =dec_to_hex function is what triggers the ToolPak error Jon describes, which is what has me perplexed.

Post by **The Robman** » Tue Jan 17, 2006 2:43 pm

Right, I understand that, but I'd still like to know if he is able to get this to work in a regular spreadsheet. If it doesn't work, then we've found the issue, if it does work, then we need to keep looking.

Mark Pierson · Post by **Mark Pierson** » Tue Jan 17, 2006 3:49 pm

The Robman wrote:If it doesn't work, then we've found the issue, if it does work, then we need to keep looking.

True, but I'm not holding out much hope knowing how quirky Excel has been through the last few versions.

I just had another though too... Jon, are you sure you have macro support enabled when you open KM? There is an outside chance that the referenced error can occur when macros are disabled. I've seen it sporadically myself while testing since Mike England and I kludged a delayed macro to overcome a previous Excel anomaly.

whompus · Post by **whompus** » Tue Jan 17, 2006 4:05 pm

As I dont use office or km I may not understand what is being talked about here. If not just overlook this.

Would that error not be because km is calling functions from the atp lib and in excel 12 the functions would now be in excel lib?

Mark Pierson · Post by **Mark Pierson** » Tue Jan 17, 2006 4:18 pm

whompus wrote:Would that error not be because km is calling functions from the atp lib and in excel 12 the functions would now be in excel lib?

Sort of... in this case, the error is caused by a renaming trick Rob used way back in the early days of KM. I use the same trick to provide support for multiple languages.

The first beta I posted was supposed to override KM's insistance on having the ATP installed. The second attempt is simply a workaround to see if my thought process is correct on what's causing the problem.

Excel doesn't make a distinction between built-in functions and those from an add-in, at least not as far as user interaction is concerned. As long as the add-in library is installed, the add-in functions can be called and used as if they were built-in.

It's been my experience that every XL release has thrown a curve ball at KM. So far, I've been able to overcome them all, so I plan on going down swinging with this one!

Mark Pierson · Post by **Mark Pierson** » Tue Jan 17, 2006 5:57 pm

One more thing just occurred to me... what if MS in its ultimate wisdom changed the names of the functions from the ATP?

Jon, can you confirm that these functions are in fact available in XL12?

BIN2DEC
BIN2HEX
DEC2BIN
DEC2HEX
HEX2BIN
HEX2DEC

If they're in there, then our renaming trick isn't going to work because as far as I know that can only be used with add-in functions and not native ones.

If they're not in there, maybe they exist with a slightly different name. If that's the case and you can identify them all, I might still be able to use them from within KM.