The SET PROCEDURE TO command should do the trick, unless one of the public variables you define is an object, whose class definition is contained in FWFUNCTS. In this case, in order to unlock the file you will need to release the object and clear the class. The following sample code releases object pcSubKey and releases the class that was used to create it:
RELEASE pcSubKey
CLEAR CLASS cSubKey
SET PROCEDURE TO (-or- RELEASE PROCEDURE fwfuncts)
If the file in question does not contain class definitions, then you should make sure that the SET PROCEDURE TO command is actually executed. Could it be that execution stops at an earlier part of the code for some reason?
FoxWeb Support Team
support@foxweb.com email |
Sent by Gary on 09/06/2002 12:00:00 PM:
I am using FW2.11 and this is my fw_enter.prg
<%
Local llRet
Set Procedure To FWFUNCTS
Do DefDlls
If Type('pcAppPath') <> 'C'
Public pcAppPath, pcAuxPath1, pcAuxPath2, pcSysAccKey, pcSubKey
Do FWLoadPaths
Endif
Do FWLoadKey
llRet = !File("ECHold.txt")
If !llRet
Response.Write('<H3>Claims system is suspended for maintenance</H3>')
Endif
Set Procedure To
Return llRet
%>
If I change some function in FWFuncts.prg, recompile, and try to transfer the new fxp to the server, it gives me a sharing violation.
If I end the channel, or stop and restart FW, I can transfer fine.
How can I find out what is causing this fxp to stay open, while all other fxps are released properly?
Gary