Re: Error in opening the Library module file


Mike wrote:
Mike wrote:
dpb wrote:
Mike wrote:
...

Then I intentionally del *.mod. I compiled again.
Error: Error in opening the Library module file. [MODT]
Error: Error in opening the Library module file. [MODA]

No longer OK. Why?

I'm thinking because you haven't done "Update Dependencies" since you
created the new project and the IDE isn't compiling all out of date
sources--in the case the modules when the .mod files don't exist.
I am guessing how I can get *.mod. Then I try following steps.
I delete section of main program and compile.
I get both of them.
Then add section of main program. Done.
Weird.......
1. I forgot to mention sequence of modules did matter.
2. I can delete the "use modA" in modT. Then I compile. I have
modT.mod.
Also delete "use modT" in modA. I have also modA.mod.
Then re-input the "use modA" in modT and "use modT" in modA.
Compile. Re-input the main program. Compile it; the results are ok.
I think I can just artificially put two *.mod files to let CVF wake up
to find the *.mod it needs.
I also find some persons also encountering such problems in CVF.
Some responder also suggest to update all dependencies; however, I
tried and
CVF failed to pick up those module files.
Originally they pick up some modules, however, they didn't pick up
modules which
are calling each other. I think this problem is called cyclic
dependencies, right?
Mike
I have done my real case, which proves the above method can solve this
question.

.

Relevant Pages