Hey Ted - thanks SO MUCH for that feedback!!! And, when I just went into the Options window, I found in the File Locations tab exactly what I thought I would see.
So, previously (last week) when I tried to launch the Code References - it would instead literally open up a particular VFP project. But, yesterday - I simply closed all my VFP open sessions, then started VFP up again - and hit Code References, and sure enough - this time around NOTHING happened. Then, after your suggestion - this morning I opened up the Options Window, looked in the File Locations tab - and sure enough I found the entry for the Code References location to be blank - as expected. As such, just now - I reset it to the actual location - and now Code References actually works. Also, now, if I do this in the command window - "? _FOXREF" - I get this now "c:\program files (x86)\microsoft visual foxpro 9\foxref.app" instead of it just printing a blank line on the screen. Now, since I was doing so much digging thru the VFP Help yesterday, I figured I would try one more search to see if I could find specific help on "Code References" - and that was indeed in the VFP Help. But, just now reading thru the Entire help page for Code References - I was surprised to find there was NO Reference at all to the Options Window & File Locations - to show where VFP points to the actual tool. Oh well - problem now Solved! Thanks again Ted - U Rock! -K ________________________________ From: ProFox <[email protected]> on behalf of Ted Roche <[email protected]> Sent: Monday, May 19, 2025 7:28 PM To: [email protected] <[email protected]> Subject: Re: Code Ref Tool is Broken... [You don't often get email from [email protected]. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] On Mon, May 19, 2025 at 4:47 PM Kurt Wendt <[email protected]> wrote: > > > But, yeah - if _FOXREF contains what VFP is trying to run - I should be able > to simply print out the value in that variable - to see what it is running. > Correct? Cause - if I do it now - it holds a blank value. > > Which does not seem right... Go to Tools, Options, File Locations tab and see what the "Code References" setting is set to. It is probably also blank. Reset it to wherever you're storing your FoxRef.app file and see what happens, after saving and turning VFP off and back on. ref: https://www.vfphelp.com/vfp9/_5WN12PZ69.htm _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/cacw6n4t72ca78fmhrqpzg5usoc6-q7jbmkx7z_0emwaigfg...@mail.gmail.com ** 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. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/by5pr13mb38438e7d3eacb806356caefec3...@by5pr13mb3843.namprd13.prod.outlook.com ** 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.
