File access slow with VFP7 & Windows XP

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Michael Loeckle - 12 Sep 2003 16:39 GMT

I am running VFP7 SP1 on a Windows XP machine with all the latest patches
and hot fixes. My problem is FoxPro's speed when Windows Explorer is open
and the network drive I am working in with FoxPro is selected. For example,
complile speed (comp *) is extremely slow. If I close Explorer or select
another drive, it's fast as ever. Windows 2000 does not seem to display
this problem. My machine is a DELL Precision 340 1.8GHz 512MB. I thought
originally there was something wrong with my installation of Windows or
something else on the machine. I formatted the drive and reinstalled
Windows XP, Office XP, Sourcesafe 6.0C, VFP7 & Project 2000. Still happens.
Any ideas? Anyone else have this problem?

Thanks,
Michael Loeckle
MicroSage, Inc.

Reply to this Message

Cindy Winegarden - 12 Sep 2003 17:09 GMT

Hi Michael,

This is certainly very strange. If you try this on another similarly
configured WinXP machine, does it occur there as well? That would lead to
suspecting something in your machine's hardware or connection to the
network. Where are the files you are compiling? What about virus software on
the machine that is slow. Is it set to scan FoxPro files? What happens if
you set it to not scan FoxPro files?

Signature

Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy.winegarden@mvps.org, www.cindywinegarden.com

> I am running VFP7 SP1 on a Windows XP machine with all the latest patches
> and hot fixes. My problem is FoxPro's speed when Windows Explorer is open
[quoted text clipped - 10 lines]
> Michael Loeckle
> MicroSage, Inc.

Reply to this Message

Michael Loeckle - 12 Sep 2003 17:45 GMT

I just installed VFP7 without VFP7 SP1 on another XP machine and it does
exactly the same thing. It is also a DELL but a different model. It has
Trend OfficeScan but my machine does not. The server has Trend installed
but my problem predates our AV installation anyway. I'm certain it's not AV
related. We have two Windows 2000 machines and they both do not have the
problem. It's got to be something with XP. I am compiling PRG files.

> Hi Michael,
>
[quoted text clipped - 21 lines]
> > Michael Loeckle
> > MicroSage, Inc.

Reply to this Message

Lee Mitchell - 12 Sep 2003 19:02 GMT

Hi Michael:

If you move the files locally and open Windows Explore, do you see the same
problem? Are you using the COMPILE command, the menu option, or the DO
command to compile the program files? Do you see the same performance
problem when opening tables on the network share? If you delete the old FXP
files before compiling do you see the problem?

What type of network (Windows 2000, Novell) are you using? What
protocol(s) are loaded on the local machine?

Where are you VFP temp files being created? Use SYS(2023) to determine
where your VFP temp files are being stored. Make sure they reside on a
local drive.

I agree with Cindy's comment on anti virus software causing performance
problems. I would disable any AV program that is running and performance
the test to make sure that is not the problem.

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 retires June 30th, 2003
- VFP6 Mainstream Support retires Sept. 30th, 2003

>I just installed VFP7 without VFP7 SP1 on another XP machine and it does
>exactly the same thing. It is also a DELL but a different model. It has
>Trend OfficeScan but my machine does not. The server has Trend installed
>but my problem predates our AV installation anyway. I'm certain it's not AV
>related. We have two Windows 2000 machines and they both do not have the
>problem. It's got to be something with XP. I am compiling PRG files.

> Hi Michael,
>
> This is certainly very strange. If you try this on another similarly
> configured WinXP machine, does it occur there as well? That would lead to
> suspecting something in your machine's hardware or connection to the
> network. Where are the files you are compiling? What about virus software

> the machine that is slow. Is it set to scan FoxPro files? What happens if
> you set it to not scan FoxPro files?
>
> > I am running VFP7 SP1 on a Windows XP machine with all the latest

patches

> > and hot fixes. My problem is FoxPro's speed when Windows Explorer is

open

> > and the network drive I am working in with FoxPro is selected. For
> example,
> > complile speed (comp *) is extremely slow. If I close Explorer or

select

> > another drive, it's fast as ever. Windows 2000 does not seem to display
> > this problem. My machine is a DELL Precision 340 1.8GHz 512MB. I

thought

> > originally there was something wrong with my installation of Windows or
> > something else on the machine. I formatted the drive and reinstalled
[quoted text clipped - 5 lines]
> > Michael Loeckle
> > MicroSage, Inc.

Reply to this Message

Michael Loeckle - 15 Sep 2003 20:35 GMT

The problem seems to be Windows XP machines and our Windows 2000 server.
Any other combination and the problem does not exist. I moved the project
directory to another 2K server and it's OK. We are going to replace the
server we are having a problem with. Not worth the time trying to figure it
out.

Thanks to everyone for the help.

Mike

> Hi Michael:
>
[quoted text clipped - 72 lines]
> > > Michael Loeckle
> > > MicroSage, Inc.

Reply to this Message

Villi Bernaroli - 17 Sep 2003 14:38 GMT

"Michael Loeckle" ha scritto

> The problem seems to be Windows XP machines and our Windows 2000 server.
> Any other combination and the problem does not exist. I moved the project
> directory to another 2K server and it's OK.

So it is not W2K server + WXP client, it is *THAT* server.

> We are going to replace the
> server we are having a problem with. Not worth the time trying to figure it
> out.

Well, maybe the problem is just that: we are experiencing files
on the Win2K server remaining unexplainably locked after using
them and releasing them (closing the app using them) from a WinXP
client.
Anyway, if you could just disable the antivirus on both the
server and the client for a while and do a test, that may prove
me wrong and solve your problem.
I read what you wrote, I'm simply use dto suspect first the
antivirus, then the antivirus again, and only after testing
without AN I start thinking to other causes.

Norton has so much bored us, with theyr default settings which
include many VFP files in the files to scan.

Vilco

Reply to this Message