I am using a lot of PRGs that I'm referencing in SET PROCEDURE TO calls.
My BizObj & DataObj classes are in the PRGs and there's a lot of OOP.
(I'm not a fan of VCX classes for BizObj and DataObj classes.)
Most likely it was as you said about the PRGs held open.
On 2014-05-18 02:39, Allen wrote:
VFP does hold compiled prg files open. Which is why you can get
problems in
debug, which should be renamed buggy as it causes more fall over's than
anything, being able to display the code. But clear all does not deal
with
them. I must admit I have never had a problem like yours, but then I
issue a
clear all in the programs anyway. Maybe the library is already open and
cannot open again? Though I don't think so. Try "Set library to" next
time,
instead of clear all, to see if that clears your problem.
I learnt something today, I didn't know about clear error.
Al
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: 18 May 2014 03:09
To: profoxt...@leafe.com
Subject: "File is not open"
VFP9SP2
Why is it when you go to rebuild your EXE, you get an error saying
"File is
not open" ?? Doing a CLEAR ALL takes care of the issue, but I'm
curious to
the reason why. I'm guessing it's one of the SET LIBRARY TOs
???
tia,
--Mike
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/73dae0b1a216105f92fc2867eede1...@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
