Software Archive
Read-only legacy content
17061 Discussions

VisBasic call to Fortran DLL

Intel_C_Intel
Employee
640 Views
I used the VisualBAsic-Visual Fortran DLL sample code (Compaq vb-example FCALL.F90) to check calling a DLL from VisBasic. Works fine on my computer but when trying to run on some other computers, I get the message: "Run time error '7'. File not found fcall.dll"
I used DEPENDS.EXE and verified the dependent dlls were in windowssystem directory.
I moved the fcall.dll and the vb executable to floppy. Runs fine on my computer. Move floppy to my lap top - get the error message. I copied DFORRT.DLL to the floppy - still get error message.
Any trouble shooting suggestions would be much appreciated.
Roger
0 Kudos
6 Replies
Steven_L_Intel1
Employee
640 Views
Is DFORRT.DLL in the Windows System folder of your laptop? It could also be in the PATH or in the directory where the VB executable is (if it's a .EXE).

On your CVF 6.5 CD in folder X86USUPPORTMISC is a program called LOADTEST.EXE. Copy this to your laptop, start a command prompt, and type: LOADTEST your-EXE It will report any problems found.

Steve
0 Kudos
Intel_C_Intel
Employee
640 Views
Steve,
Confiming that DFORRT.DLL is in the windows system folder. I just copied it there - does it need to be registerred??

Based on other forum messages, compiled dll using static libs istead of dll libs - ran ok.

I don't have LOADTEST.EXE on my cd (version upgrade 6.x to 6.5). Is it available to download??

Thanks for help.
Roger
0 Kudos
Steven_L_Intel1
Employee
640 Views
Here

Steve
0 Kudos
Intel_C_Intel
Employee
640 Views
Ran loadtest in A: drive of lap top.
Loadtest FCALL.DLL - "The specified module could not be found"

Loadtest Project.exe - "One of the library files needed to run this application could not be found"
0 Kudos
Steven_L_Intel1
Employee
640 Views
Very strange. LOADTEST doesn't link against any non-standard DLLs. Please e-mail your fcall.dll to me at fortran@compaq.com so that I can take a look at it. What Windows version is your laptop?

Steve
0 Kudos
Intel_C_Intel
Employee
640 Views
Steve,

Tried moving MSVCRT.DLL to floppy. Still ng. But along the way, I
believe I found the problem. Using DEPENDENCY WALKER (came up when I
used explorer and double cliked on the dll), showed DFORRT.DLL "doesn't
appear to be WIN32 module..." Recopied DFORRT.DLL to floppy and voila,
runs ok. So I guess DFORRT.DLL got contaminated along the way.

Steve, thank you again for your patient support. VERY MUCH APPRECIATED.

Roger
0 Kudos
Reply