I have just started using VX in some spare time to learn the
keys and all that good stuff.  However, after I run the
program using F9, I cannot run it that way again without
closing the program (VX) and coming back in and doing it
again.

It gives me an error that says (from memory):
	You don't have access to the following:
	my.exe
	Close everything that has access to it 
	Do you want to continue?

Is there something I am doing wrong?  All the program is
currently is a APPSYS and MAIN (the ones VX created) and a
message box.

- richard hankins

"A Sign At the Electric Company: "We will be delighted if
you send in your bill. However, if you don't, you will be.""

On Wed, 26 Jan 2005 12:58:23 -0600, Richard L. Hankins, Jr.
wrote:

> It gives me an error that says (from memory):
> 	You don't have access to the following:
> 	my.exe
> 	Close everything that has access to it 
> 	Do you want to continue?

I have that fixed, for some reason VX did not like me
running it on a linux server partition.  Linux was not
releasing the hold on the exe for some reason or another.

- richard hankins

"Friends help you move. Real friends help you move bodies."

Oops, closed that one out before I got done putting what my
current issue is.

To fix the other problem, I had to move my project off the
debian server and put it on my computer. (it is on my
desktop to be exact) And I have begun getting a new error
(See Attached)  it does not run the executable at all.... so
I am unsure of what the problem is... it is more like it is
letting me know everything is ok 

- richard hankins

"We are Microsoft. Resistance Is Futile. You Will Be
Assimilated."

Did you do a install or just copy the VX files from the server??? I 
think VX must be "installed"

Jim

Richard L. Hankins, Jr. wrote:
> Oops, closed that one out before I got done putting what my
> current issue is.
> 
> To fix the other problem, I had to move my project off the
> debian server and put it on my computer. (it is on my
> desktop to be exact) And I have begun getting a new error
> (See Attached)  it does not run the executable at all.... so
> I am unsure of what the problem is... it is more like it is
> letting me know everything is ok 
> 
> 
> ------------------------------------------------------------------------
>

On Wed, 26 Jan 2005 18:13:11 -0500, James Loughner wrote:

> Did you do a install or just copy the VX files from the server??? I 
> think VX must be "installed"
> 
> Jim

Well, VX is installed on my local computer.  Only the
project I created was initially on the linux server.  

I was thinking maybe the path the project was too long, so I
moved it from the DESKTOP on my XP machine to
"C:\ASI\PRNDRV" instead and opened it in VX... now, it will
run the program and everything properly (with F9) the first
time, but now I am getting the original error again... 

The program is quite simple...



//////////////////////////////////////////////////////////////////////

  Copyright:
        Your Copyright goes here., (c) 2000. All rights
reserved.

  Contents:
        This is a standard win32 exe.

//////////////////////////////////////////////////////////////////////

#include "Common.ch"
#include "FileIO.ch"

/* Overloaded AppSys which does nothing
 */
PROCEDURE AppSys

   /* use the ANSI charset by default */
   SET CHARSET TO ANSI

RETURN

/* This is our main procedure
 */
PROCEDURE Main
  Local oP

  MsgBox("X")

  QUIT

RETURN

- richard hankins

"If white wine goes with fish, do white grapes go with
sushi?"

Is the exe readonly??

Jim

Richard L. Hankins, Jr. wrote:
> On Wed, 26 Jan 2005 18:13:11 -0500, James Loughner wrote:
> 
> 
>>Did you do a install or just copy the VX files from the server??? I 
>>think VX must be "installed"
>>
>>Jim
> 
> 
> Well, VX is installed on my local computer.  Only the
> project I created was initially on the linux server.  
> 
> I was thinking maybe the path the project was too long, so I
> moved it from the DESKTOP on my XP machine to
> "C:\ASI\PRNDRV" instead and opened it in VX... now, it will
> run the program and everything properly (with F9) the first
> time, but now I am getting the original error again... 
> 
> The program is quite simple...
> 
> 
> 
> //////////////////////////////////////////////////////////////////////
> 
>   Copyright:
>         Your Copyright goes here., (c) 2000. All rights
> reserved.
> 
>   Contents:
>         This is a standard win32 exe.
> 
> //////////////////////////////////////////////////////////////////////
> 
> #include "Common.ch"
> #include "FileIO.ch"
> 
> /* Overloaded AppSys which does nothing
>  */
> PROCEDURE AppSys
> 
>    /* use the ANSI charset by default */
>    SET CHARSET TO ANSI
> 
> RETURN
> 
> /* This is our main procedure
>  */
> PROCEDURE Main
>   Local oP
> 
>   MsgBox("X")
> 
>   QUIT
> 
> RETURN
> 
> 
> 
> 
> ------------------------------------------------------------------------
>

Richard,
have you got any virus-scanning software active? Try to disable that and 
retry.

HTH,
Martin

No, the file is not read only... it is like it never quits
running. The Attribs on the file are only archive, the exe
is not listed as a process or a running program.  But I
cannot delete it or anything until I close down VX.  But
when I close down VX the EXE is deleted.

I am wondering if it is something I am doing with F9... when
I hit f9 the program runs in debug mode... do I have to hit
something to stop debug mode even though the application has
stopped?

Also, I do not have any virus software that constently scans
the hard drive... the only time it checks it is when I tell
it to.  But I did try disabling it all together.

- richard hankins

"It may be that your sole purpose in life is simply to serve
as a warning to others."

Hi Richard,
if you start a program with F9, it runs until you stop it by yourself (there
is a menuitem - just dont know how it is called for I dont have VX running
at this time - something like Reset Program) or until it stops naturally by
user interaction or it crashes. If you have a breakpoint somewhere the
program stops there but debugger is still running and holds the exe open.
You can go on just by another pressing of F9 (this doesnt restart the
program but it is running from the last breakpoint or from the last line you
were moving to with step by step mode on).
If you change code while debuggimg (yes this is possible) the next time you
press F9 VX wants to recompile everything before going on and if the exe is
still open from the debugger, linking fails. There should be an option you
can adjust somewhere in VX settings to give you a warning in this situation
and you can click to Go on (that will automatically stop last debugging
session before recompiling) or cancel.
HTH
Klemens

"Richard L. Hankins, Jr." <RHankins@ContactASI.com> schrieb im Newsbeitrag
news:1v47b449c5gp3$.1k861w56noutr.dlg@40tude.net...
> No, the file is not read only... it is like it never quits
> running. The Attribs on the file are only archive, the exe
> is not listed as a process or a running program.  But I
> cannot delete it or anything until I close down VX.  But
> when I close down VX the EXE is deleted.
>
> I am wondering if it is something I am doing with F9... when
> I hit f9 the program runs in debug mode... do I have to hit
> something to stop debug mode even though the application has
> stopped?
>
> Also, I do not have any virus software that constently scans
> the hard drive... the only time it checks it is when I tell
> it to.  But I did try disabling it all together.
>
> - richard hankins
>
> "It may be that your sole purpose in life is simply to serve
> as a warning to others."

On Mon, 14 Feb 2005 16:03:28 +0100, Klemens Lichter wrote:

> Hi Richard,
> if you start a program with F9, it runs until you stop it by yourself (there
> is a menuitem - just don´t know how it is called for I don´t have VX running
> at this time - something like Reset Program) or until it stops naturally by
> user interaction or it crashes. If you have a breakpoint somewhere the
> program stops there but debugger is still running and holds the exe open.
> You can go on just by another pressing of F9 (this doesn´t restart the
> program but it is running from the last breakpoint or from the last line you
> were moving to with step by step mode on).
> If you change code while debuggimg (yes this is possible) the next time you
> press F9 VX wants to recompile everything before going on and if the exe is
> still open from the debugger, linking fails. There should be an option you
> can adjust somewhere in VX settings to give you a warning in this situation
> and you can click to Go on (that will automatically stop last debugging
> session before recompiling) or cancel.
> HTH
> Klemens
> 
> "Richard L. Hankins, Jr." <RHankins@ContactASI.com> schrieb im Newsbeitrag
> news:1v47b449c5gp3$.1k861w56noutr.dlg@40tude.net...
>> No, the file is not read only... it is like it never quits
>> running. The Attribs on the file are only archive, the exe
>> is not listed as a process or a running program.  But I
>> cannot delete it or anything until I close down VX.  But
>> when I close down VX the EXE is deleted.
>>
>> I am wondering if it is something I am doing with F9... when
>> I hit f9 the program runs in debug mode... do I have to hit
>> something to stop debug mode even though the application has
>> stopped?
>>
>> Also, I do not have any virus software that constently scans
>> the hard drive... the only time it checks it is when I tell
>> it to.  But I did try disabling it all together.
>>
>> - richard hankins
>>
>> "It may be that your sole purpose in life is simply to serve
>> as a warning to others."

Thanks a million Klemens!

That has been bugging the crap out of me... I have been
making all my changes F9 test them unload vx reload vx and
start again... 

- richard hankins

"Confession is good for the soul, but bad for your career."

On Tue, 15 Feb 2005 13:33:14 -0600, Richard L. Hankins, Jr.
wrote:
> 
> Thanks a million Klemens!
> 
> That has been bugging the crap out of me... I have been
> making all my changes F9 test them unload vx reload vx and
> start again...

(note: this is the original VX not the 1.9)

I have just gotten to test this out, and apparently that is
not it.... when I run the program with F9 it runs and
executes just fine, then exits like normal.  After it is
done running, I look in the menu and I cannot choose reset
project (Ctrl+f2) it seems like it is already reset.  But
for some reason VX does not release its lock on the file.
It is very odd and I cannot figure out what is happening... 

Not sure if it has anything to do with it, but I am going to
try the oplock stuff... maybe that is what is happeneing...
I don't think I have oplocks off on this machine... I am all
out of ideas.

- richard hankins

"We are born naked, wet, and hungry. Then things get worse."