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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

My Code Reference tool not saving items 2

Status
Not open for further replies.

Bryan - Gendev

Programmer
Jan 9, 2011
408
AU
I thought I saw the solution to this before but have searched and can't find it.
Anyone help?

GenDev
 
What exactly do you mean by "not saving items"? Code References just displays its results. It does not save anything.

It would be helpful if you could say what you expect to happen, and what is actually happening.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads
 
Code references creates a table for its results wwith the name projectname_ref.dbf (and cdx and fpt), if you do a project search. So there'd be a code references result table per project.
I'm quite sure there will be other DBFs if you don't search a prject but a directory, there are several modes in which code references can be used.

Well, either you're not searching the project, or a copy of the project without a copy of that table projectname_ref.dbf table (which is in the same directory as the pjx. Didn't you recreate a pjx from scratch? That'll not restore this projectname_ref table.

Anyway, it's true code references stores its results and if you don't find them again, it's not the end of the world, is it? I mean results become outdated, when code moves because of new lines of code or removed lines of code, the results can become wrong pretty fast when you explicitly make changes to the code locations found. Information about line numbers is not updated when you change the code, for example. So the only relevant results are the last results anyway.

The stored results are not accelerating searches, they are just stored results of what was correct at the time of search. You do experiencee faster searches after you did one, but that's not an effect of these stopred results tables acting as an index, that's simply caching what was read in the first search, which accelerates further searches, even for totally different search terms, VFP is just having a lo of the source code in cached memory the second and further times you search.

Well, if you sill would like to look into previous search results the best thing to do is earch for *_ref.dbf files, there's a chance for finding some of that.

Chriss
 
OT:

mjcmkrsr said:
Did you try Gofish 7?

Thank you for the link Mark.

I didn't realise there was a new version of GoFish, I was still using GoFish5.

Regards,

David

Recreational Developer and End User of VFP for my personal use in 'Amateur Radio' and 'British Railways' related Applications.
 
I have used the listing in Code References as a quick way to get to areas of my project which I have checked before - most useful - and you can re-search when needed too.
I have successfully recovered my long list from my backup folder.

TRhanks

GenDev
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top