Invalid PRO/FMO file error in VdB5.7

[Bob Newman]

Yeah, I'm still maintaining an app in this version. Recently we've been getting the Invalid PRO/FMO file Internal Error message when running the .exe, and it's always the same .cc/.co file causing it. I recompile the .cc and create a new .exe and the error goes away. But the next month when we create a new .exe for distribution it is back again.

The last time this happened I noted that the .co was more recent than the .cc, but when I ran the program from the command window the .co was rebuilt with the current date. Almost as if the system saw something wrong with the .co file. The last change to the .cc was in July, but the error began appearing in September. Any ideas???

[Bob Newman]

Well, it happened again this month with the same file. ia_state.co generates an Invalid pro/fmo error message. Here's the general sequence of events:

compile the cc to co and generate my app.exe during the month. The app.exe works fine. Just before monthly release (no changes to ia_state.cc) I generate a new app.exe and distribute. Client runs app.exe and gets the Invalid pro/fmo error. I get the same error.

I look at the date stamp on the .cc and .co files... 11/04 and 11/05 respectively. I run the app from the command window and dBase creates a new .co with today's date, 11/10. Create a new app.exe and the error is no more.

Anybody have any ideas what may be going on here? This has happened for three straight months. It's as though the .co gets corrupted just sitting on the server; no additional changes to the .cc, and when the app.exe is created it uses the corrupt .co file.

Post by Bob Newman
Yeah, I'm still maintaining an app in this version. Recently we've been getting the Invalid PRO/FMO file Internal Error message when running the .exe, and it's always the same .cc/.co file causing it. I recompile the .cc and create a new .exe and the error goes away. But the next month when we create a new .exe for distribution it is back again.
The last time this happened I noted that the .co was more recent than the .cc, but when I ran the program from the command window the .co was rebuilt with the current date. Almost as if the system saw something wrong with the .co file. The last change to the .cc was in July, but the error began appearing in September. Any ideas???

[Ken Mayer [dBVIPS]]

says...

Post by Bob Newman
compile the cc to co and generate my app.exe during the month. The app.exe works fine. Just before monthly release (no changes to ia_state.cc) I generate a new app.exe and distribute. Client runs app.exe and gets the Invalid

pro/fmo error. I get the same error.

Post by Bob Newman
I look at the date stamp on the .cc and .co files... 11/04 and 11/05 respectively. I run the app from the command window and dBase creates a new .co with today's date, 11/10. Create a new app.exe and the error is no more.
Anybody have any ideas what may be going on here? This has happened for three straight months. It's as though the .co gets corrupted just sitting on the server; no additional changes to the .cc, and when the app.exe is created it

uses the corrupt .co file.

Post by Bob Newman

Post by Bob Newman
Yeah, I'm still maintaining an app in this version. Recently we've been getting the Invalid PRO/FMO file Internal Error message when running the .exe, and it's always the same .cc/.co file causing it. I recompile the .cc and

create a new .exe and the error goes away. But the next month when we create a new .exe for distribution it is back again.

Post by Bob Newman

Post by Bob Newman
The last time this happened I noted that the .co was more recent than the .cc, but when I ran the program from the command window the .co was rebuilt with the current date. Almost as if the system saw something wrong with the

.co file. The last change to the .cc was in July, but the error began appearing in September. Any ideas???
Bob,
If the app.exe is created with the .co, why do you still distribute the
.co? It's in the app.exe. You only need to distribute the .co if it is
more current than the one inside the app.exe (assuming you are using the
DEO ability to do this).

Um, check the version ... 5.7 doesn't have that ability (DEO).

Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm
http://www.goldenstag.net/dbase

[Geoff Wass [dBVIPS]]

In article <***@news-server>, ***@_nospam_goldenstag.net
says...

Post by Ken Mayer [dBVIPS]
Um, check the version ... 5.7 doesn't have that ability (DEO).
Ken

Ken,

LOL. I did it again. Thanks for catching that.

[Geoff Wass [dBVIPS]]

In article <***@news-server>, ***@rhodussystems.com
says...

Post by Bob Newman
compile the cc to co and generate my app.exe during the month. The app.exe works fine. Just before monthly release (no changes to ia_state.cc) I generate a new app.exe and distribute. Client runs app.exe and gets the Invalid

pro/fmo error. I get the same error.

Post by Bob Newman
I look at the date stamp on the .cc and .co files... 11/04 and 11/05 respectively. I run the app from the command window and dBase creates a new .co with today's date, 11/10. Create a new app.exe and the error is no more.
Anybody have any ideas what may be going on here? This has happened for three straight months. It's as though the .co gets corrupted just sitting on the server; no additional changes to the .cc, and when the app.exe is created it

uses the corrupt .co file.

Post by Bob Newman

Post by Bob Newman
Yeah, I'm still maintaining an app in this version. Recently we've been getting the Invalid PRO/FMO file Internal Error message when running the .exe, and it's always the same .cc/.co file causing it. I recompile the .cc and

create a new .exe and the error goes away. But the next month when we create a new .exe for distribution it is back again.

Post by Bob Newman

Post by Bob Newman
The last time this happened I noted that the .co was more recent than the .cc, but when I ran the program from the command window the .co was rebuilt with the current date. Almost as if the system saw something wrong with the

.co file. The last change to the .cc was in July, but the error began appearing in September. Any ideas???


Bob,

If the app.exe is created with the .co, why do you still distribute the
.co? It's in the app.exe. You only need to distribute the .co if it is
more current than the one inside the app.exe (assuming you are using the
DEO ability to do this).

[Bob Newman]

I don't distribute the .co; the app.exe generates the error, i expect because it contains the corrupt .co.

says...

Post by Bob Newman
compile the cc to co and generate my app.exe during the month. The app.exe works fine. Just before monthly release (no changes to ia_state.cc) I generate a new app.exe and distribute. Client runs app.exe and gets the Invalid

pro/fmo error. I get the same error.

Post by Bob Newman
I look at the date stamp on the .cc and .co files... 11/04 and 11/05 respectively. I run the app from the command window and dBase creates a new .co with today's date, 11/10. Create a new app.exe and the error is no more.
Anybody have any ideas what may be going on here? This has happened for three straight months. It's as though the .co gets corrupted just sitting on the server; no additional changes to the .cc, and when the app.exe is created it

uses the corrupt .co file.

Post by Bob Newman

Post by Bob Newman
Yeah, I'm still maintaining an app in this version. Recently we've been getting the Invalid PRO/FMO file Internal Error message when running the .exe, and it's always the same .cc/.co file causing it. I recompile the .cc and

create a new .exe and the error goes away. But the next month when we create a new .exe for distribution it is back again.

Post by Bob Newman

Post by Bob Newman
The last time this happened I noted that the .co was more recent than the .cc, but when I ran the program from the command window the .co was rebuilt with the current date. Almost as if the system saw something wrong with the

.co file. The last change to the .cc was in July, but the error began appearing in September. Any ideas???
Bob,
If the app.exe is created with the .co, why do you still distribute the
.co? It's in the app.exe. You only need to distribute the .co if it is
more current than the one inside the app.exe (assuming you are using the
DEO ability to do this).
--
Geoff Wass [dBVIPS]
Montréal, Québec, Canada
.|.|.| dBASE info at http://geocities.com/geoff_wass |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.
.|.|.| IT Consultant http://Geoff_Wass.com |.|.|.

[Geoff Wass [dBVIPS]]

In article <***@news-server>, ***@rhodussystems.com
says...

Post by Bob Newman
I don't distribute the .co; the app.exe generates the error, i expect because it contains the corrupt .co.

Bob,

Maybe it is a virus or hardware fault that corrupts that file.

[Bob Newman]

May have found the cause of the problem, at least this time. I viewed the good and the bad app.exe in a hex editor (and it was ugly). The part with the ia_state.co had some extra "]" characters and was missing some code. I tried to delete what I thought was the corrupt .co and got an access denied message. It appears that MacAfee had the file locked up. I suppose the exe build just included the locked .co and moved on. We recently acquired a utility to release files so affected.

Post by Bob Newman
compile the cc to co and generate my app.exe during the month. The app.exe works fine. Just before monthly release (no changes to ia_state.cc) I generate a new app.exe and distribute. Client runs app.exe and gets the Invalid pro/fmo error. I get the same error.
I look at the date stamp on the .cc and .co files... 11/04 and 11/05 respectively. I run the app from the command window and dBase creates a new .co with today's date, 11/10. Create a new app.exe and the error is no more.
Anybody have any ideas what may be going on here? This has happened for three straight months. It's as though the .co gets corrupted just sitting on the server; no additional changes to the .cc, and when the app.exe is created it uses the corrupt .co file.

Post by Bob Newman
Yeah, I'm still maintaining an app in this version. Recently we've been getting the Invalid PRO/FMO file Internal Error message when running the .exe, and it's always the same .cc/.co file causing it. I recompile the .cc and create a new .exe and the error goes away. But the next month when we create a new .exe for distribution it is back again.
The last time this happened I noted that the .co was more recent than the .cc, but when I ran the program from the command window the .co was rebuilt with the current date. Almost as if the system saw something wrong with the .co file. The last change to the .cc was in July, but the error began appearing in September. Any ideas???

[Geoff Wass [dBVIPS]]

In article <***@news-server>, ***@rhodussystems.com
says...

Post by Bob Newman
May have found the cause of the problem, at least this time. I viewed the good and the bad app.exe in a hex editor (and it was ugly). The part with the ia_state.co had some extra "]" characters and was missing some code. I tried

to delete what I thought was the corrupt .co and got an access denied message. It appears that MacAfee had the file locked up. I suppose the exe build just included the locked .co and moved on. We recently acquired a utility to
release files so affected.
Bob,

A false positive (ie. a good file mistakenly identified as containing a
virus). That sounds plausible. You should be safe to tell Macafee to
exclude your .co files.