Foxpro and Open Files and Backup and Win 2000 Server

Hello - I have a client who has problems with backup because files from my VFP
application remain open even after users exit the application. He has made
sure that all workstations have exited my application and yet the server still
shows that files are open. He is blaming my application. I say it is the
responsibility of the server or workstation to properly close out files when
users exit my application.

I have noticed that when a workstation is accidentally reset or when it freezes
some servers will keep files open (like phantom files). Why doesn't the server
close these files? I have heard there is a setting in Win 2000 that may be
applied so that if a workstation is reset or logs off - all related files are
closed. This specific client has Win 2000 server sp4 and win 2000
workstations. All ideas appreciated.

Thanks,

Mike

Leemi
Thu Jan 29 14:02:04 CST 2004

Hi Mike:

I am not an expert on file handling on a Windows 2000 Server. To cover all
your bases, you might want to post this question to a Windows 2000 Server
newsgroup as well. There might be some registry settings that would be of
value. Disabling Opportunistic locking is one setting that comes to mind.

822219 You Experience Slow File Server Performance and Delays Occur When You
http://support.microsoft.com/?id=822219

However, I would not implement any of these registry changes until you gain
a through understand of their implications.

Are you running any anti virus software? Some anti virus software
aggressively scans files for virus and many hold a file lock on the object
longer. Here is an article on how to prevent Norton AV from scanning our
files:

321550 HOWTO: Optimize Visual FoxPro Applications While Using Norton
AntiVirus
http://support.microsoft.com/?id=321550

You can try to implement the same idea (ignoring VFP data files) with
other AV software packages.

You also may want to try the command in this article. Since the basic
problem is open files that prevent a backup, you may be able to run a .BAT
file to close all the open files and thus resolve the issue in this manner.


290585 How to Close All Files Opened by Network Clients from the Command
Line
http://support.microsoft.com/?id=290585

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retires Sept. 30th, 2003


>Hello - I have a client who has problems with backup because files from my
VFP
>application remain open even after users exit the application. He has made
>sure that all workstations have exited my application and yet the server
still
>shows that files are open. He is blaming my application. I say it is the
>responsibility of the server or workstation to properly close out files
when
>users exit my application.

>I have noticed that when a workstation is accidentally reset or when it
freezes
>some servers will keep files open (like phantom files). Why doesn't the
server
>close these files? I have heard there is a setting in Win 2000 that may be
>applied so that if a workstation is reset or logs off - all related files
are
>closed. This specific client has Win 2000 server sp4 and win 2000
>workstations. All ideas appreciated.

>Thanks,

>Mike

Andrew
Tue Feb 03 07:59:30 CST 2004

MAppell917 wrote:
> Hello - I have a client who has problems with backup because files
> from my VFP application remain open even after users exit the
> application. He has made sure that all workstations have exited my
> application and yet the server still shows that files are open. He
> is blaming my application. I say it is the responsibility of the
> server or workstation to properly close out files when users exit my
> application.
>
> I have noticed that when a workstation is accidentally reset or when
> it freezes some servers will keep files open (like phantom files).
> Why doesn't the server close these files? I have heard there is a
> setting in Win 2000 that may be applied so that if a workstation is
> reset or logs off - all related files are closed. This specific
> client has Win 2000 server sp4 and win 2000 workstations. All ideas
> appreciated.

A bit different but we use an excellent product called St Bernard Open File
Manager to back up our dbf files whilst they are in use.
http://www.stbernard.com/

I believe the server will close the file resources eventually but I'm not
sure what controls it. I believe NT saves time by leaving the resource open
for an amount of time because the chances are the workstation will request
the file lock again quite soon and it saves the OS having to rush off and do
that again.

--
HTH
Andrew Howell

John
Mon Feb 09 20:36:17 CST 2004

Andrew, Make sure that you are closing and clearing everything before
you exit your application. Some 'Quit' routines can be quite lengthy.
Win 2000 server only keeps open files that the workstation tell it to
leave open.

Use Filemon on the workstation and watch what you are opening. I found
a bunch of stuff and cleaned it up so now once all workstations have
gone back to desktop, the backup is run immediately before they close
the store down for the night.


Andrew Howell wrote:
> MAppell917 wrote:
>
>>Hello - I have a client who has problems with backup because files
>>from my VFP application remain open even after users exit the
>>application. He has made sure that all workstations have exited my
>>application and yet the server still shows that files are open. He
>>is blaming my application. I say it is the responsibility of the
>>server or workstation to properly close out files when users exit my
>>application.
>>
>>I have noticed that when a workstation is accidentally reset or when
>>it freezes some servers will keep files open (like phantom files).
>>Why doesn't the server close these files? I have heard there is a
>>setting in Win 2000 that may be applied so that if a workstation is
>>reset or logs off - all related files are closed. This specific
>>client has Win 2000 server sp4 and win 2000 workstations. All ideas
>>appreciated.
>
>
> A bit different but we use an excellent product called St Bernard Open File
> Manager to back up our dbf files whilst they are in use.
> http://www.stbernard.com/
>
> I believe the server will close the file resources eventually but I'm not
> sure what controls it. I believe NT saves time by leaving the resource open
> for an amount of time because the chances are the workstation will request
> the file lock again quite soon and it saves the OS having to rush off and do
> that again.
>
> --
> HTH
> Andrew Howell
>
>

anonymous
Sun May 09 06:46:02 CDT 2004

I've been running Terminal Services and Visual Fox for a year now and the only time that I have had a problem is when I have a user set up to 'disconnect from session' for non-use. I changed the setting to 'end session' and the problem went away.