Paging any Excel 2010 64-bit gurus
Posted: Sat May 15, 2010 2:27 pm
I've about reached my level of incompetence with the Excel Add-In with this version of Excel. It almost works, but there are a couple of gotchas that I've been scratching my head over for a while and have reached a dead end.
1) There's a single function that is called by all Add-In functions that adds a hidden note to the produced plot, describing the source reference, e.g. "Source: [examples.xls]ZGrid!B6:AG37". Works swell in Excel 2010 32-bit and all previous versions of Excel, but for some reason I can't fathom this crashes Excel 2010 64-bit.
2) The precursor to the Add-In, dplotlib.xls, works fine with Excel 2010 64-bit (after commenting out the function mentioned in #1). But if I try to save as either a new .xlam Add-In or the old .xla format, Add-In functions work (sometimes) once, but never twice. The second time (and sometimes the first) has always resulted in a crash of Excel.
If you feel like you're in the know about 64-bit Excel, or even if you just want to take this for a spin, please contact me at support@dplot.com. You'll be able to fiddle around with the VBA code as much as you'd like. Any pointers would of course be most welcome.
1) There's a single function that is called by all Add-In functions that adds a hidden note to the produced plot, describing the source reference, e.g. "Source: [examples.xls]ZGrid!B6:AG37". Works swell in Excel 2010 32-bit and all previous versions of Excel, but for some reason I can't fathom this crashes Excel 2010 64-bit.
2) The precursor to the Add-In, dplotlib.xls, works fine with Excel 2010 64-bit (after commenting out the function mentioned in #1). But if I try to save as either a new .xlam Add-In or the old .xla format, Add-In functions work (sometimes) once, but never twice. The second time (and sometimes the first) has always resulted in a crash of Excel.
If you feel like you're in the know about 64-bit Excel, or even if you just want to take this for a spin, please contact me at support@dplot.com. You'll be able to fiddle around with the VBA code as much as you'd like. Any pointers would of course be most welcome.