You can perfectly use the 2007 SDK to build XLLs that will be compatible with Excel 2003. All you have to do is avoid using new features of the 2007 SDK (the documentation talks about them). The 2007 SDK is built in such a way that new calls are in an include file rather than in the import library, so your XLL should load with Excel 2003 w/o an issue.
-- Danny Khen Excel Program Manager, Microsoft Corp. [To use my email address, replace (dot) and (at) with respective chars, and (MSFT) with microsoft.com.]
** This posting is provided "AS IS", with no warranties, and confers no rights. ** "Jesper Lund" <usenet[ at ]jesperlund.com> wrote in message news:%23oiSFrkJJHA.4936[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text] > JoeLiuzzo wrote: > >> I built an XLL years ago (in 2001) which worked when I was running Excel >> 2000 under Win 2000. I haven't had need of it again till recently, but >> when I try to open it using Excel 2003 (under XP), it's not recognized >> as an XLL. > > An XLL binary which worked 7 years ago, should work in Excel 2003. Could > it be that your XLL depends on other DLLs that are not present on the new > system? If the XLL cannot initialize itself properly (missing DLLs in > $PATH, or exceptions generated by your own C++ class instances in global > scope), Excel will report that that the XLL "could not be recognized". > >> I am guessing I need to re-build the XLL. But when I looked for the >> appropriate SDK, I see one titled '2007 SDK'. My company has not yet >> moved to EXCEL 2007. > > Unless you want to cater for the new possibilities in Excel 2007 (like > string longer than 255 chars, bigger arrays, or multithreaded functions), > there is no urgent need to use the 2007 SDK. The old one will suffice. On > the other hand, it doesn't hurt to prepare for the future :-) > > -- > Jesper Lund
|