Can't recompile - .fxp seems 'locked'

[massoc]

I am trying to recompile a .prg but I am getting a message that I can't create the .fxp when I compile. If I try to rename the .fxp before compiling, it says it is in use by another peron or program. Is there anyway I can tell who/what is holding the .fxp? This is Accpac pro series and I have everyone off the system, etc. Any help/guidance would be appreciated. thanks.

 

[wgcs]

Try:

CANCEL
CLEAR ALL

If you still can't compile, then exit and restart VFP. Works every time.

If anyone has a better answer, I'd like to hear it, too!

 

[rgbean]

CLEAR PROGRAM should be sufficient, but CLEAR ALL will work too!

Rick

 

[massoc]

Thanks for the input. however, it doesn't seem to be a vfp lock on the .fxp. I can close out of vfp and then go to the directory that the .fxp is in and try to rename it and I get the message stating that the file is in use. I guess that I need to shut down the box that the file is on to break the connection that is holding it. All users are off of the system and that is why I don't think it is a valid user/process that is holding it. Do you know how you can tell what process/user could be holding this file?
thanks

 

[rgbean]

Is this file on your local system, or on a network drive? If networked, what OS is the file server running?

Rick

 

[ramani]

You can use the Ctrl+Alt+Del key which activate the WIndows Task Manager, then check all the processes. This could throw some light on your applications process which are open.

____________________________________________
ramani - (Subramanian.G)

http://winnersoft.coolfreepages.com/

 

[mspratt]

You could possibly find out what and when with either the File Monitor or Process Explorer available at:

http://www.sysinternals.com/

(free)

Regards,

Mike

 

[dbMark]

Most likely this is a file shared on the network and someone is running it. Depending on the file server you use, you should be able to display all files currently open from the server console and determine who has them open or who the server thinks has them open. Even if all users are off the server sometimes old links remain, especially if their computer crashed, power glitch or they turned off the computer without shutting down.

Often, when you change the code in the .PRG you can save it just fine since users only access the program file's pre-compiled .FXP file. Find the user(s), have them exit, and you should compile it just fine.

If you create .EXE files for the users to run, then you should have no trouble compiling. Of course then when you want to replace the .EXE application with a newer version you will hit that file-in-use issue at that point.