Sharing I/O controls blocks between dll and static exe

[martymike]

My basic question is "can you do it?" (see subject line)

To explain: we have a library of utility programs, one of which opens a file and returns a unit number (I'm omitting all the other arguments that can be specified for this routine). Normally we have no problem with this, but now we have two.

A little background: we are currently building our production projects with CVF 6.6B and I am attempting to port everything over to IVF 9.1 and having many many issues with the new version of Microsoft Studio. (Microsoft has assigned a support person who has answered most of my questions.) One issue we have had concerns what I call "builder programs"; they are are small applications that we have written that generate code, usually in the form of Include files. We found that they would always rebuild, even if nothing changed (in the new version of Studio, that is). We learned that this was due to the manifest files that were being added to the executables (a case of the cure being worse than the disease, imho). This, of course, cascaded into causing them to run, causing everything using those includes to rebuild, ..., you get the point. The solution is to build those programs statically.

Hence problem number 1: when one of these builder programs (built with /libs:static /threads) runs it calls the utility program I referred to above, but write statements produce files named fort.xx (where xx is the unit number) rather than the file named in the open statement. If I build with /libs:dll /threads then all is well.

Problem number 2 has been around for a while. This concerns the current builds using the CVF compiler,and we've been hoping it will "go away" when we finish the conversion to IVF. But, since we are on the subject, ... : It appears that when the library is on a network drive, but the executable is local, that we have the same problem. Copy the library to my C drive, no problem.

Any ideas?