Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Does anyone know why Code References Search is sloooooow sometimes?
- Thread starter GriffMG
- Start date
- Thread starter
- #21
- Thread starter
- #22
I have a solution, and a possible explanation.
The solution first. Delete some files in (for me)
C:\Users\Administrator\AppData\Roaming\Microsoft\Visual FoxPro 9
The ones called Refdef.* and RefFile.*
These files contain list of the files you have opened and where you 'were' in them etc. so when you reopen a file in the IDE it comes back where you were working before.
The snag is when you work on many projects with similar file names the CR process can't use an index to differentiate between the files, because the path is stored in a memo field - which can't be indexed - and takes an age to locate the right entry (I think).
Delete the files and you lose your defaults - like opening a project on a new PC - but at least CR whizzes through things.
B-)
Why does it only do this slooow dooown sometimes, dunno - perhaps it tidies up from time to time?
Regards
Griff
Keep [Smile]ing
There are 10 kinds of people in the world, those who understand binary and those who don't.
The solution first. Delete some files in (for me)
C:\Users\Administrator\AppData\Roaming\Microsoft\Visual FoxPro 9
The ones called Refdef.* and RefFile.*
These files contain list of the files you have opened and where you 'were' in them etc. so when you reopen a file in the IDE it comes back where you were working before.
The snag is when you work on many projects with similar file names the CR process can't use an index to differentiate between the files, because the path is stored in a memo field - which can't be indexed - and takes an age to locate the right entry (I think).
Delete the files and you lose your defaults - like opening a project on a new PC - but at least CR whizzes through things.
B-)
Why does it only do this slooow dooown sometimes, dunno - perhaps it tidies up from time to time?
Regards
Griff
Keep [Smile]ing
There are 10 kinds of people in the world, those who understand binary and those who don't.
TamarGranor
Programmer
That's not correct. Your location in the editor for each file is stored in FoxUser.DBF.
The files you mention appear to be Code References local store for what it's learned about your files.
That said, you may be correct that those files getting big slows the tool down.
I tried GoFish this week for the first time. It flies.
Tamar
- Thread starter
- #24
Tamar,
I'm sure you're right - but zapping those files did exactly what I said, and it seems to make CR go like a blast.
So, I'm happy.
Regards
Griff
Keep [Smile]ing
There are 10 kinds of people in the world, those who understand binary and those who don't.
I'm sure you're right - but zapping those files did exactly what I said, and it seems to make CR go like a blast.
So, I'm happy.
Regards
Griff
Keep [Smile]ing
There are 10 kinds of people in the world, those who understand binary and those who don't.
- Status
Similar threads
- Locked
- Question