Re: Compile - file is not open error

I am logging in as Administrator. I am the only one who uses this computer.
Everything is on the local drive. This is on XP Pro. Luckily I am not
dealing with the Vista UAC issues yet.

Thanks,
Cathy


"Dan Freeman" <spam@xxxxxxxxxxxxx> wrote in message
news:OwBaogV9HHA.5360@xxxxxxxxxxxxxxxxxxxxxxx
Sounds more like a permissions problem to me.

Dan

Cat Chowdy wrote:
Some projects do have project classes. However if I just create a
simple hello world type prg and compile it I still get the error.

I uninstalled and reinstalled VFP9 and SP1 and still get the problem.

This is happening on my desktop (XP Pro SP2). I also have VFP9 on
an old, little used WIN2K laptop. I copied a project over to the
laptop and compiled and it worked fine...which leads me to believe it
is not a project problem. Feels like a trashed dll problem or
something similar.
I think I will have to go through the VFP9 folder and compare files
between the desktop and laptop. I hope it is not something in any
windows folders.
Any other suggestions appreciated.

Thanks,
Cat


"Josh Assing" <XjoshX@xxxxxxxxxxx> wrote in message
news:qhqee3dhkbju8i0safisro209s45jlmj9g@xxxxxxxxxx

Sounds vaugely familiar... Do you have any project classes? (like
something to
add in manifests or something)

On Tue, 11 Sep 2007 15:03:38 -0500, "Cat Chowdy"
<catchowdyathotmaildotcom>
wrote:

Yes I have.

The project builds fine. The application builds fine. But when it
gets to
"building executable" on the statusbar I get the file is not open
error. After exiting the error message, I find that it has created
an exe about 43KB. The normal exe is about 4.8MB. If I run the
exe, I get a file open dialog looking for a type of fxp.

It's not just this project, I get the same error trying to build an
exe for
all my VFP9 projects.

I have an old VFP5 project that builds the exe just fine.

I guess my next step is uninstalling and reinstalling VFP9 and SP1.

Thanks,
Cat


"Josh Assing" <XjoshX@xxxxxxxxxxx> wrote in message
news:c0sde3dota0mfn5o0a9mas9tqelrgiqt0g@xxxxxxxxxx
have you tried "recompile all"?

On Mon, 10 Sep 2007 17:46:12 -0500, "Cat Chowdy"
<catchowdyathotmaildotcom>
wrote:

VFP9 SP1

At the end of a compile to an exe I am getting a "file is not
open" error.
The last compile I did was a month ago and everything worked fine.
Today
I
am getting the file is not open error when trying to compile all
of my vfp9
apps. The only reference I could find to this is something that
happened
in
VFP6 and was fixed by a service pack.

Help please...
Cat




.

Relevant Pages

  • Re: Compile - file is not open error
    ... I uninstalled and reinstalled VFP9 and SP1 and still get the problem. ... The normal exe is about 4.8MB. ... At the end of a compile to an exe I am getting a "file is not open" ...
    (microsoft.public.fox.helpwanted)
  • Re: Compile - file is not open error
    ... simple hello world type prg and compile it I still get the error. ... I uninstalled and reinstalled VFP9 and SP1 and still get the problem. ... The normal exe is about 4.8MB. ... I guess my next step is uninstalling and reinstalling VFP9 and SP1. ...
    (microsoft.public.fox.helpwanted)
  • Re: Compile - file is not open error
    ... I uninstalled and reinstalled VFP9 and SP1 and still get the problem. ... "building executable" on the statusbar I get the file is not open error. ... The normal exe is about 4.8MB. ... At the end of a compile to an exe I am getting a "file is not open" ...
    (microsoft.public.fox.helpwanted)
  • Re: Compile - file is not open error
    ... I uninstalled and reinstalled VFP9 and SP1 and still get the problem. ... "building executable" on the statusbar I get the file is not open error. ... The normal exe is about 4.8MB. ... At the end of a compile to an exe I am getting a "file is not open" ...
    (microsoft.public.fox.helpwanted)
  • Re: VB application crashes
    ... I have created an VB application with a MDI form and a lot of ... In VB6, in the project's properties, go to the Compile tab and select ... Run the EXE from Windows Explorer. ... Make sure that you disable "Create symbolic debug info" before releasing ...
    (microsoft.public.vb.general.discussion)