Not Enough Disk Space

[Auguy]

I have a VFP9 app that has the database and data tables on a network drive. Once in a while the program throws some errors: "There is not enough disk space for l:\hhdata$\data\orders.fpt", "Error reading file l:\hhdata$\data\schedule.cdx", "Error reading file l:\hhdata$\data\datafiles.dbc". Also saw "Foxcode table not found, is not correct version or is incompatible." Is this a Fox problem, or something comimg from the network causing these errors. Any ideas would be helpful.

Auguy
Northwest Ohio

 

[dgrewe]

I have seen this when:
1. The network administrator limited in the amount of disk space a User could use.

2. (If you are using Oracle or and Older version of MSSQL) the back end Database engine ran out of Alloted Disk Space.

David W. Grewe Dave

 

[Auguy]

Thanks David.

This is an all Foxpro app, program and data.
99% of the time there is only one user.

Auguy
Northwest Ohio

 

[Mike Lewis]

Auguy,

Sorry if this is an obvious question, but is it possible that you have indeed run out of disk space? I know it's unlikely, but worth checking.

Also, David's point about the user having a personal disk space limit is a good one - even in a single-user system.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk

 

[Auguy]

Thanks, I don't think the space limit is the problem, but will certainly double check with the network folks to be sure. These errors don't happen often, so I have a hard time believing it is a space issue. This is a VFP9 SP1 program. Should I update to SP2? I thought I read where there were major problems with SP2.

Auguy
Northwest Ohio

 

[craigber]

I doubt disk space problems would cause read errors on the .dbc. My guess is there is a network problem. Perhaps a bad connector, hub, wiring, network card.

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[Mike Lewis]

I strongly doubt that upgrading to SP2 would solve the problem. This sounds more like a problem with the physical environment or network rather than a VFP bug.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk

 

[Dan Freeman]

I'll agree with the other that this is environmental.

When VFP attempts to write to a file (i.e. INSERT or APPEND BLANK, etc.) it doesn't actually write to the file. It asks the OS to do it.

If the OS replies "NO!" then VFP really has no idea what the real reason is, it just gives the error message that seems the closest match. This used to be a bugbear on Novell networks when the owner of a file was deleted as a user.

The OS never says "No, because..." -- it just says "NO!".

These network issues can range from a flaky NIC to a router that drops a packet here or there to a staple through the LAN cable that runs through a storage room. A million things can cause it.

They can be difficult to pin down, but with dilligent observation you should eventually find it.

 

[Auguy]

Thanks to all!

Auguy
Northwest Ohio