Ted,
On closer examination, what I actually did, was give a simpler name to the
directory that contained all of the auxilary files so I could study them
more easily. This effectively erased the origional files. The Clean up
command with the original directory just put FoxPro into an infinite loop.
With the new directory, it works. If Clean up fails now, I can easily erase
the whole directory. Strangly enough I could not map a drive letter to the
origional directory--another XP quirk, I suppose.
Kenn Leland
----- Original Message -----
From: "FoxPro" <foxpro AT adelphia DO.T net>
To: "ProFox Email List" <profox@leafe.com>
Sent: Saturday, November 29, 2003 12:58 AM
Subject: Re: FoxRef in Win XP still doesn't work WORKS
> Ted,
>
> I took advantage of the option of "Cleaning up Source tables" and
everything
> works now.
>
> Thanks,
> ----- Original Message -----
> From: "Ted Roche" <tedroche AT tedroche DO.T com>
> To: "'ProFox Email List'" <profox@leafe.com>
> Sent: Friday, November 28, 2003 3:16 PM
> Subject: RE: FoxRef in Win XP still doesn't work
>
>
> Kenn:
>
> By FoxRef do you mean the VFP Code References tool? I've been using it
with
> some success on WinXPPro for a while now, although it's not exact on line
> number hits. I would suspect you might have a problem with the particular
> source you're running it on. Are you using it in project or directory
mode?
> Can you test it on different sources?
>
> There are options to clear out the reference files it builds up over time,
> and you may also want to ZAP them manually. ProjectName_Ref.* files are
> stored with the project, and Ref*.* and similar file names are stored in
> C:Documents and SettingsYourNameApplication DataMicrosoftVisual
FoxPro
> 8
>
> -----Original Message-----
> From: profox-bounces AT leafe DO.T com [mailto:profox-bounces@leafe.com] On Behalf
> Of FoxPro
> Sent: Friday, November 28, 2003 4:54 PM
> To: ProFox Email List
> Subject: FoxRef in Win XP still doesn't work
>
>
> A while back I complained in this mail list about FoxRef not working in
Win
> XP although it worked in other versions of windows. Someone pointed me to
> the Source code for this routine in the VFP files and I have studied it a
> bit. I am still baffled. Sometimes it works and sometimes it just seems
to
> go into an infinite loop (100% processing and "not responding"--also
> occasional copmplaints about "insufficient memory") I do not know if this
> is unique to my installation of XP or is an XP wide problem. Any
> suggestions would be welcome. This is a very welcome tool--when it works!
> I do know that it is writen in VFP 8 and can not run in VFP 7.0 (it uses
> collections and Try-Catch). My machine is a 2.5 GHz pentium with 1GB RAM
> and 400 GB HD.
>
> Kenn Leland
> The Software Connection
>
> --- StripMime Report -- processed MIME parts ---
> multipart/alternative
> text/plain (text body -- kept)
> text/html
> ---
>
[excessive quoting removed by server]
©2003 FoxPro |
