>>>I found the problem. If the project name has a period in the middle of the filename, Code References generates the "_ref" file without the ".dbf" extension. Therefore, when time comes to display the search result, it can not find the file with the ".dbf", and therefore assumes there were no result from the search.
>>>
>>>Either I need to change my naming convension for filename in my most recent application, or not to expect the Code references to work as expected.
>>
>>There's third choice. You can submit bug to MS and try to fix the Code References and rebuild the application. Fixing could be as easy as adding '.' to the following list in the foxref.h

* The following are invalid in an alias name so we replace with '_'
>>#define INVALID_ALIAS_CHARS	" -@#$%^&*()+={}[]:;?/<>,\|~`'" + ["]
>>

>
>Excellent suggestion. That fixed it.
>
>As for reporting it as a bug. In normal file naming, one generally does not put periods to seperate the words. I saw it being done in the .NET world, and throught it as a nice way of specifing sib modules of a parent application. I could have used the underscore just as easly.
>

Hi Greg,

Glad that my guess was correct. :)
I still think it's a (very minor) bug because '.' is a legit character in a file name.