The compile suddenly brings strange errors.
First compile brings: * File i-o error: program.idy
then the 2nd compile brings: program.OBJ : error LNK2001: unresolved external symbol __mFerr3
Does anyone have an idea?
Regrds,
Georg
Application Delivery Management
Application Modernization & Connectivity
CyberRes
IT Operations Management
The compile suddenly brings strange errors.
First compile brings: * File i-o error: program.idy
then the 2nd compile brings: program.OBJ : error LNK2001: unresolved external symbol __mFerr3
Does anyone have an idea?
Regrds,
Georg
Hi Georg,
When you state that this problem "suddenly" appeared is this implying that this program used to compile without errors and now this error occurs?
A couple of questions:
What has changed between the time where it worked and the time where it fails?
- product update?
- program change?
- environment change?
Does this happen on all programs or just this one?
If it happens on all programs then you might want to try doing a Repair on Net Express.
Hello Georg, after closing netexpress, please delete all files in the debug und release directory and recompile your project and show the result!
On what os do you had install netexpress 5.1 ? Win7 - Win10 or Win11
Do you remember, long time we had seen us in Bad Honnef!?
Yes, I remember. We looked at List&Label. Now I use Version 27.
Regards, Georg
Hi Chris,
I think it's because of Windows updates. I rarely use the notebook with my second license.
My development PC(W7) is in repair.
I have done a repair, but same result.
ok, yes, i use also LiLa 27 und all files/data are under sql, no isam-files.
Do you use also Visual Cobol x.x?
It will be time to have a new contact! What do you mean?
not yet, OK my email is gj@gjsoft.onmicrosoft.com
Chris,
after the repair I have delete the release and debug folder.
The first compile of the project was ok, but the 2nd brought the file i-o error.
Are the release and debug folders on a network drive by any chance? We have seen a similar issue before when a network drive was being used. If you are compiling to a network drive can you try your C drive instead?
It is a SSD in the NB.
Anyway I will copy the project to the c: drive and recompile it.
I will inform you about the result immediately.
Unfortunately all programs have the message * File i-o error: progname.idy