I saw this in the FAQ:
Can I build a VF DLL that is linked against the VF static libraries?
We strongly recommend that you NOT do this as it can cause subtle and difficult to analyze application errors. If you build a DLL, always link against the shared libraries.
Can anyone elaborate on why I shouldn't do this? I create Fortran DLLs that are called using EXCEL VBA. A lot of the code in the DLL is the same across various projects so I placed these into a static library. Therefore, a programmer working on a new project only needs to modify the project specific code and link with the static library. Sounds like a reasonable thing to do.
I'm not an expert on the inner workings of DLLs, so I'd appreciate info that anyone can provide.