I have corrected these and looking for others such anomalies.īut despite of these corrections the calculations are still not working. So far I have only found these two but there could be others as well. its changing "Lon" to "Long", "Da" to "Days" etc. Windows is changing some parameter names in my UDFs on its own e.g. In my scrutiny so far, I have noticed some weird things that windows/excel2016 is doing to my file.Ī.
I will use your suggestion of copying it part by part in separate files and test. I am now in the process of scrutinizing the later code (which is lot to review). The later versions use a different method of calculations which do not seem to work somehow. About the Author s Michael Alexander is a Microsoft Certified Application Developer (MCAD) and author of sev- eral books on advanced business analysis with Microsoft Access and Microsoft Excel. Right now I am trying to go back to older versions of my file and I have found that a late 2013 version is working fine but all other versions since then do not work. It is not MISSING it is just not available in. Following migration of Excel to the Office365 64-bit version the library reference to it (in MS Project Standard 2010) is no longer available. Image 3: Re-opening the menu shows that the incorrect PDFCreator version is selected. I have VBA code native to MS Project Standard 2010 which manipulates the Excel 2016 Application by early binding via the Excel 16.0 Object Library reference. I have not tried yet copying parts of code on different files as yet will try it out now. Image 1: Default state of the VBA Project References (PDFCreator not selected) Image 2: Selecting the correct PDFCreator version. Yes, some of the UDFs use an external dll file which resides in the same directory as this file as well as I have copied it in the system directory.
0 kommentar(er)
