Hi Jan thanks for that post and link - I did research and even installed it to test it - no difference. DLL is not present in the WOW64 bit folder, and I am reluctant to try and add a dll and register it without further research.
I found a couple of forum posts regarding this topic, including work arounds that were mainly related to coding rather than what is existing. It is also more related to people using access databases on 64bit servers, with access users still using microsoft 2003, rather than 2007 / 2007.
It has something to do with references X86 machines.. after that point I felt it was over my head.
However, I did install that exe on the server, and tested it on a catalook site and had to revert back because the xls file I was using would not import.
There was a hotfix for this but it was related to Windows 2003 64bit machines, not Windows 2008 64 bit machines.
http://www.chilkatsoft.com/downloads_... that is the mail component I think being used in a bulk email app which was a redistributable dll packaged with the module and was running on the client site, which caused me some grief. I can't remember exactly what the confict was, but because the site was running on the .net 4 framework after an upgrade, I was not comfortable with taking it backwards to 3.5 and changing the config files as I had other small challenges with things already registered.
I have read in a few places, issues people are having with .net 4 framework, not all dnn related but some are.
So thanks Jan for this very informative link. I think after I finished I had a sense of dejavu because I've tried so many work arounds and I've not looked back on our documentation to see exactly what I did to solve a problem.
I appreciate your research time and suggestion. I do have our local development server and might try out the manual registration of the dll on the server to test first, after I've finished the 1/2 dozen upgrades I'm doing at the moment.
Nina Meiers