Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

help with *.mod errors

dars
Beginner
710 Views
I am novice programmer. I have a visual fortran program that was working fine until, I believe, I installed a visual basic program that likely overwrote some files.
My program (Compaq visual fortran 6.6) uses f90VB libraries to, for example, initiate an Explorer instance or an Excel instance. I am using f90VBDefs, f90VBVariants, and f90VBAutomation modules (using, of course, use statements within my program). I have insertedthe libraries into the program. Nothing appears to have changed from before (looking at the *.plg build log files). However, I am now getting errors informing me that the program cannot find the f90VBDefs.mod., the automation.mod, and the variants.mod files.
Obviously I do not understand the mechanics to a sufficient degree to know why I am getting this error. And, I cannot remember how to view the library files to see if the modules are present. This just makes no sence to me. Can someone help?
0 Kudos
1 Reply
Jugoslav_Dujic
Valued Contributor II
710 Views
However, I am now getting errors informing me that the program cannot find the f90VBDefs.mod., the automation.mod, and the variants.mod files.
There are actually two types of files you need to pull in when you get a F90 library -- .mod files and object files (usually .libs, sometimes .objs). .Mod files are requiredduring compilation time, so that the compiler can see declarations that come from F90 MODULEs -- every MODULE Foo produces a Foo.mod file during compilation of file containing Foo. .Lib files are required during link-time, and they contain actual assembly code to be executed.
By default, f90 compiler searches for external .mod files in directories listed in Tools/Options/Directories/Include files. I guess that VB installation screwed that list somehow -- find f90VBDefs.mod file on your disk (that comes from your f90VB installation) and make sure that directory is in that list, i.e. add it if it's missing.
Similarly, in "Library files" category are listed files where .libs are searched for -- if you get a LNK2001 error during link stage, probably that directory is screwed too; apply the same cure.
Jugoslav
0 Kudos
Reply