Derek,
Which version of VFP did you find this in? I'm interested if the same fault
is still within VFP9 in which case it may well be a good idea to press the
team for a fix whilst they are still around. 

I must admit I've never come across the problem and we run about 150 screens
here so I'd be interested in seeing the code which you reckon can show the
problem if you wouldn't mind.

Dave Crozier

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Derek Kalweit
Sent: 29 March 2007 14:53
To: [email protected]
Subject: Re: DBC File Scan/Access (was Re: Foxpro going opensource)

> I've seen a lot of extraneous traffic, similar to what you've described.
>
> The pinpointed things to change were:
>  - search paths for the exe
>    'set path to' in any prg or method
>    'path=' in the config.fpw file

Searching the paths is nothing compared to this problem.


>  - stripping out the paths in the forms prior to compilation.
>    changing 'data\george.dbc' to 'george.dbc'
>
> I made some code for a projecthook that runs prior to the actual build of
> the exe that strips out stuff in the forms - paths were only one thing
> that it does.  I had built it into 'beforebuildevent' method.

The problem I describe isn't searching for the file-- it's the
excessive re-reading of the dbc header-- a file it already has open.

FYI, if the DBC is marked readonly, this doesn't occur. The VFP
support tech suggested this, which I believe the VFP team mentioned--
so they know the code which is excessively reading the header, it
seems, as they've specifically put code in to not re-read constantly
if it's readonly...  Obviously having a read-only DBC causes other
problems, particularly during data update routines. One of the
proposals to solve our problem was to manage the readability of the
DBC files, making it writable for data structure changes, etc, and
readonly otherwise, but the risk was high, as it causes data
corruption if VFP needs to write to the DBC for something and can't...


-- 
Derek


[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** 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.

Reply via email to