I am using Fortran DLLs together with VBA Excel since many years. The configuration so far was Windows 7 (x32), Excel 2013 (x32) and MS Developer Studio Fortran PowerStation 4.0 (1994!) also x32. This works without any problems. I recently moved to a more powerful computer (a Dell precision with NVIDIA) with Windows 10 (x64) and Excel 2019 (x64). Therefore my x32 DLLs do not work anymore. I changed the platform because I am developing a larger and more complex model, which is too slow on the old platform (it works though). Since I want to use GPU acceleration, the PGI Fortran compiler seems to me the obvious choice. I found reports of people using the Intel Fortran compiler for DLLs used with Excel x64, but no reports using the PGI compiler.
The PGI Fortran generated DLLs do not work with my VBA code. When I run the VBA code I get an error (Error code 53: cannot find file "MyDll.dll").
you can try java open source platform library to use this.
instead of PGI and Fortran.
Java is open source and install able in every platform
alternately you can use C program Visual C++ library
its better choice to do this.
Dear Adnan,
Thank you for your thoughts. Unfortunately, it is not so simple. This is quite a large code and it needs very efficient computation (hence GPU acceleration). The PGI Fortran compiler (using Open ACC or CUDA) is a pretty good choice; Java or Visual C++ are not a good replacement.
Unfortunately, there are not many researchers using PGI compilers together with Excel, so it is difficult to get help.
Cristian
Is "MyDll" the real name of your DLL ? My first guess is that the DLL of the PGI compiler and/or the DLL's it depends on (if any) is/are not on the PATH used by VB...
Dear Bart,
Yes, "MyDll" is the DLL that I created. I did check the path settings and they seem OK. However, although I do have a path set on the place where the PGI redistributables are, MyDll would not find them unless I copy those into the same directory as MyDll. This is strange in itself and I don't understand. Having said this, I checked the dependencies of MyDll using a Dependency Walker. I found that MyDll finally finds the PGI DLLs and also the VS17 DLLs (which PGI uses). The error seems to root at a lower level (kernel32.dll and kernelbase.dll). This is too deep for me. I am more an algoritms person, without much knowledge of computer science...
I'm also much more interested in algorithms...
Just one though : why does your DLL depend on kernel32 if you compiled it as a 64bits stuff ? Are you sure you provided the correct parameters to your compiler to produce a 64bits output ?
The compiler in its current version only supports 64 bit. Your question is good. I learned that on a 64 bit machine the kernel32.dll is a 64 bit version. I find it missleading,but I suppose MS has their reasons...
For moving from a x86 to a x64 platform, you need to do the followings:
IMPORTANT: You may need to modify your code before compiling as a x64 library depending on weather you have used memory dependent variables (e.g., pointers).
Not so important: Because you have changed your computer, make sure that the VB is searching the right directory for MyDll.dll. You may need to add the directory to the Environment Variables (PATH).
Dear Yazdan,
I am sorry for the late answer... I lost sight of the project for a while due to Corona...
Can you recommend a good and modern Dependency Walker? I have been using two programs so far: Depends V2.2.6000 (vintage 2006!) and Dependencies V1.1. There are problems... first they show different dependency results; second, they list some 150 unresolved DLL dependencies... I should say that my Windows and VS installations are OK. I ran multiple checks and all is as it should be...
I also loaded DLL-Files.com Client, which gives you access to tested official DLLs and registers them automatically. It works really well; I can recommend.
Still, after doing all this, I still didn't manage to solve the problem.
I used to employ InstallShield in the company I worked for formerly. It is basically a software tool for creating installers or software packages. When you add a dll or exe file to the package, it automatically tracks the dependencies and asks you if you want to include them in the package as well.
- Badges
- Science topic