That is a great link to JKP-ADS website, but is pretty complicated.
Right now, the jkp code makes two assumptions,
#1 the entire addin has changed location.
#2 the addin code would be modified by me to reference my particular functions using a string (the jkp code starts with one function named "UDFDemo(".
#2 is easily accomodated by coding For Each udfname in array("myfunc1", "myfunc2" etc)
Assumption #1 is harder to accomodate because the addin has not simply changed location. It is only a single funtion that has moved from xlstartBob to xlstartProd. Even worse, sometimes xlstartBob has an "improved" version of a function in that is also in xlStartProd. In those cases, I could code Environ("Username") = "Bob" to decide which version to use. Or, a slightly cleaner approach would be to create a registry entry like "UseProdOrTestAddin" to make the decision. And, of course on my computer, xlstartProd and xlstartBob will both open simultaneously, so other interference might crop up.
So, if I decide to use the JKP code, I will certainly have a bunch of work to do. Right now I am leaning torward my orginal idea of creating a clone of xlstartBob with "stubs" for each of the functions like FirstNumber = Application.Run("'xlstartP
Also, there is one other quirk in our configuration that works to my advantage. The C:drive xlstartProd workbook only has about 20 lines of code. That code does a read only open of another workbook \\server02\xlstartProdRout
I'm going to leave this question open over the weekend, just in case anybody wants to post comments.
Thanks for your help
Main Topics
Browse All Topics





by: roryaPosted on 2009-10-09 at 01:47:33ID: 25533199
You may want to have a look at this article by Jan Karel Pieterse on this subject: http://www.jkp-ads.com/Art icles/FixL inks2UDF.a sp
Regards,
Rory