MACRO will not work in my new windows 8.1 and Office 2013

[Zebra7860]

I have a Macro SWEDLL32.DLL file that I placed in my laptop in the path "windows/system 32" and where I also have my Office 2003 and that macro works perfectly. This spreadsheet does all the computations without issues.

However, recently I bought a WIndows 8.1 64 bit computer and also bought Office 2013. When I placed that file in the same path - "windows/system 32" or where My excel path is: "C:\Program Files\Microsoft Office 15\root\office15\EXCEL.EXE"

What do I have to do to make this macro work on my new computer? Which path do I have to place it in?

You can also email me at zebra7860@yahoo.ca

Thanks in advance!

[HansV]

Welcome to Eileen's Lounge!

I have moved this thread from the Windows 10 folder to the Excel folder.

Do you have Swiss Ephemeris? If so, the file should probably be in the folder C:\sweph\bin, and you need to add this to your PATH environment variable - see The AstroPatterns User's Guide.

[Zebra7860]

Hi Hans,

This macro was created for me and based on my memory it was also based on a Swiss Ephemeris, so what you say makes sense. However, I am not sure I understand
the rest of your reply. I can't seem to find the C:\sweph\bin path and what else you mentioned as well. Sorry to sound dense...

Al

[Rudi]

Are you running 64-bit version of Excel or the 32-bit version?

[Zebra7860]

not sure what version of I am using, to be honest. I tried to right click on the Excel icon and it did not state anything. My computer is 64 bit, if that helps. How would I go about finding the version of Excel? Remember that it is the 2013 version...

[Rudi]

Hope this is big enough to follow...

bitlevel13.png

If not...see here

BTW: Welcome to the lounge from me too...

[Zebra7860]

Hi Rudi,

Well, I learnt something new. My Excel version is 32 bit.

Thanks
Al

[HansV]

Thanks. Try placing the DLL in C:\Windows\SysWOW64 instead of in C:\Windows\System32.

[Zebra7860]

I honestly thought that this would work but sadly it does not. A buddy of mine got this spreadsheet to work by placing it in Windows/system 32, but he switched over to Windows 10 - Could that be the culprit? I hear too many negative things about Windows 10, so I dont want to download it.

[Rudi]

All the searched from Google turn up issues with the 64bit version of Office, hence my question. I am not finding any issues listed with Excel 32bit, so I am not sure what more I can suggest?

[Zebra7860]

Nothing more you can suggest. I appreciate all your help. Thanks!

[HansV]

Could you do the following?

- Open the workbook.
- Press Alt+F11 to activate the Visual Basic Editor.
- Select Tools > References...
- The references used by the workbook have their check boxes ticked.
- Is there a reference in use to SWEDLL32.DLL? It might start with MISSING.

[Zebra7860]

Hi,

I have uploaded the references snapshot. No such reference to Swed32.dll

[HansV]

I don't see a screenshot, but I take you on your word. That's one less thing to check.

[Zebra7860]

Here it is again. My apologies

[HansV]

Thanks, that confirms what you wrote.

[HansV]

By the way, what is the text of the error message that you get when you try to run the macro?

[Zebra7860]

There is no text of the error message. I have values which don't update when I click on the "+" or "-" buttons that increment time and it results in the value " #VALUE! " for those fields.

If you compare this with the spreadsheet that works on another computer, I get actual values instead of "#VALUE! "

[Zebra7860]

Here is a snipet of what I am saying. I am sure that you have seen something like this before.

Thanks again for all your help. I don't know if anybody can figure this one out, but I do appreciate the response

[Rudi]

I speak under correction, but if Excel could not read the dll's or UDF's then the error would be #NAME! instead of #VALUE! So the fact that it is #VALUE! (IMHO) tells that its possibly not a library read fail or a VBA fail, but rather a data fail in the sheet. Are you sure you are providing the correct values for the calculations? IOW if you are providing numbers to the app, are they actual numbers (not text) or if you are providing dates, are they actual serialized dates and not text dates?