Message "CodeFileNotFound" is produced either by module Stores or module Interpreter (when using dynamical loading of modules by Dialog.Call). It seems your program trying to call some command from external module by Dialog.Call, which tries to load it at run time. But it fails, because corresponding .ocf file was not found.
I propose to import all need modules in order to replace all occurrences of Dialog.Call in caller module. After that, add these modules to parameters of DevLinker.
I guess, this should solve a problem.
2011/7/19 Douglas G. Danforth <danforth{([at]})nowhere.xy
Folks,
Another hair puller outer!
I have generated a .exe file that works in the BlackBox directory
but does not work when moved to some other directory.
Yes, it is using a third party dll that is resident in c:\WINDOWS\system32
and is not resident anywhere else (i.e. it is not in the BB directory).
So why should the .exe file work when placed in the BB directory
but not in some other directory?
The fact that it works at all says it does find the .exe file (when in the BB
directory).
Now I really do not know whether it is the third party dll that is causing the
problem since the only error message I get is
CodeFileNotFound
which could be referring to any code file. But then again the fact that the
.exe file works when placed in the BB directory says that all of the necessary
Component Pascal code files have been included in the linkage and packing
steps (doesn't it?).
So, I really don't know how to proceed from this point.
Suggestions welcome.
-Doug Danforth
---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy
---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy
Received on Tue Jul 19 2011 - 10:25:34 UTC