'premfin2.exe is not an object file' The documentation indicates that this means the file has an invalid header. I had the customer deinstall and reinstall the application from the. I loaded Proventure onto my old Windows XP computer. Now I have Windows 8 & cannot open the files! I loaded Proventure onto my old Windows XP computer. Now I have Windows 8 & cannot open the files! The file extensions are.DBF,.DBT, &.DBX..fxp is not an object file. For additional information click the following link.
Hi; I have a VFP 5.0b application that I have distributed in multiple locations and they have all been working great until today. One of my customers purchased another package that is based on Foxpro (I am not sure what version). After the new Foxpro app was installed, when the VFP5.0b exe was run, an error came up right away; 'premfin2.exe is not an object file' The documentation indicates that this means the file has an invalid header. I had the customer deinstall and reinstall the application from the distribution CD, which did not resolve the problem. I also ensured that the 2 Foxpro apps have unique Foxuser and Config.fpw files. Any helpful hints would be appreciated.
Mon, 13 Dec 2004 05:07:57 GMT. I found the following in knowledge base SYMPTOMS If you run an executable installed from disk images created by the Visual FoxPro Setup Wizard, the following error message appears: ' is not an object file.' Note that the size of the executable installed on the destination machine is larger than the original.
RESOLUTION There are two possible workarounds to this situation: Distribute an additional file that is named alphabetically first. For example, if there is only one file being distributed and it is named 'myexe.exe,' add an additional file named 'a.txt.' If possible, use the NetSetup images instead of diskette images created by the Setup Wizard.
STATUS Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This has been corrected in Visual FoxPro 6.0.
MORE INFORMATION The three criteria that cause this error are: The.EXE to distribute must be large enough to have the Setup Wizard split it into separate files for distribution. The split files must spread across more than one diskette image. The.EXE file name must be the first file, alphabetically, of the files being distributed via the Setup Wizard hope this helps. Hi; I have a VFP 5.0b application that I have distributed in multiple locations and they have all been working great until today.
One of my customers purchased another package that is based on Foxpro (I am not sure what version). After the new Foxpro app was installed, when the VFP5.0b exe was run, an error came up right away; 'premfin2.exe is not an object file' The documentation indicates that this means the file has an invalid header.
I had the customer deinstall and reinstall the application from the distribution CD, which did not resolve the problem. I also ensured that the 2 Foxpro apps have unique Foxuser and Config.fpw files. Any helpful hints would be appreciated. Mon, 13 Dec 2004 06:05:29 GMT. I found the following in knowledge base SYMPTOMS If you run an executable installed from disk images created by the Visual FoxPro Setup Wizard, the following error message appears: ' is not an object file.' Note that the size of the executable installed on the destination machine is larger than the original.
RESOLUTION There are two possible workarounds to this situation: Distribute an additional file that is named alphabetically first. For example, if there is only one file being distributed and it is named 'myexe.exe,' add an additional file named 'a.txt.' If possible, use the NetSetup images instead of diskette images created by the Setup Wizard.
STATUS Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This has been corrected in Visual FoxPro 6.0. MORE INFORMATION The three criteria that cause this error are: The.EXE to distribute must be large enough to have the Setup Wizard split it into separate files for distribution. The split files must spread across more than one diskette image. The.EXE file name must be the first file, alphabetically, of the files being distributed via the Setup Wizard hope this helps Hi; I have a VFP 5.0b application that I have distributed in multiple locations and they have all been working great until today. One of my customers purchased another package that is based on Foxpro (I am not sure what version). After the new Foxpro app was installed, when the VFP5.0b exe was run, an error came up right away; 'premfin2.exe is not an object file' The documentation indicates that this means the file has an invalid header.
I had the customer deinstall and reinstall the application from the distribution CD, which did not resolve the problem. I also ensured that the 2 Foxpro apps have unique Foxuser and Config.fpw files. Any helpful hints would be appreciated.
Mon, 13 Dec 2004 23:44:14 GMT. The setup disk was created from a NETSETUP directory. The application (exe) was working fine for several months until the other FoxPro app was installed.
Any other thoughts? I found the following in knowledge base SYMPTOMS If you run an executable installed from disk images created by the Visual FoxPro Setup Wizard, the following error message appears: ' is not an object file.' Note that the size of the executable installed on the destination machine is larger than the original. RESOLUTION There are two possible workarounds to this situation: Distribute an additional file that is named alphabetically first. For example, if there is only one file being distributed and it is named 'myexe.exe,' add an additional file named 'a.txt.'
If possible, use the NetSetup images instead of diskette images created by the Setup Wizard. STATUS Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This has been corrected in Visual FoxPro 6.0.
MORE INFORMATION The three criteria that cause this error are: The.EXE to distribute must be large enough to have the Setup Wizard split it into separate files for distribution. The split files must spread across more than one diskette image.
The.EXE file name must be the first file, alphabetically, of the files being distributed via the Setup Wizard hope this helps Hi; I have a VFP 5.0b application that I have distributed in multiple locations and they have all been working great until today. One of my customers purchased another package that is based on Foxpro (I am not sure what version). After the new Foxpro app was installed, when the VFP5.0b exe was run, an error came up right away; 'premfin2.exe is not an object file' The documentation indicates that this means the file has an invalid header. I had the customer deinstall and reinstall the application from the distribution CD, which did not resolve the problem. I also ensured that the 2 Foxpro apps have unique Foxuser and Config.fpw files. Any helpful hints would be appreciated.
Thanks! Tue, 14 Dec 2004 08:21:08 GMT. You wrote on Fri, 28 Jun 2002 21:10:12 GMT: RH No I don't use Refox. And the author of another VFP program? Maybe even different versions of VFP support files may affect.
Try to reinstall you program and see, if it will help. If it help to launch your program, but stop another program from working, just put all the nesassary dll's to your program folder and to this new program folder (don't remember exact list of support files for VFP5, so try to figure it by youself). WBR, Igor Sat, 18 Dec 2004 01:09:14 GMT.
Hi; I have a VFP 5.0b application that I have distributed in multiple locations and they have all been working great until today. One of my customers purchased another package that is based on Foxpro (I am not sure what version). After the new Foxpro app was installed, when the VFP5.0b exe was run, an error came up right away; 'premfin2.exe is not an object file' The documentation indicates that this means the file has an invalid header.
![Foxpro Foxpro](http://res.cloudinary.com/engineering-com/image/upload/v1486027464/tips/screenshot.165_ce4amm.png)
![Not Not](http://img.over-blog-kiwi.com/1/43/54/07/20151203/ob_7f95f3_demo2.jpg)
I had the customer deinstall and reinstall the application from the distribution CD, which did not resolve the problem. I also ensured that the 2 Foxpro apps have unique Foxuser and Config.fpw files. Any helpful hints would be appreciated. Sat, 18 Dec 2004 06:11:14 GMT Page 1 of 1 8 post.