VFP9 Code References Problem

[OldManOBIE]

Every time I close the code references window, VFP quits. This just started happening this week and I can't think of any changes to the system. Any suggestions?

 

[GriffMG]

Well it's not normal behaviour.

I'm assuming you aren't clicking on the wrong X button B-)

I would start by clearing any existing FDXREF files from your project folder and trying again.

After that I would reinstall VFP

Then I would come here and ask again... and someone would tell me what I had done wrong (probably) B-)


Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[Dan Freeman]

What an odd symptom! I don't think I've ever seen this one reported before.

Does this happen only in certain directories? Certain projects? Certain searches? Or does it always happen?

In addition to cleaning out FDXREF files, you might try renaming foxuser.* files. They've been known to cause all sorts of mayhem.

 

[OldManOBIE]

Thanks for the suggestions.

It happens in all projects and all directories. I have re-installed VFP 9 and SP2. I deleted the foxuser.*, ref*.dbf and *_ref.dbf files. I could not find any fdxref files.

I even deleted the registry "HKET_CURRENT_USER\Software\Microsoft\VisualFoxPro" entry.

I don't know what else to try, short of re-installing Windows.

 

[GriffMG]

If you have done a search in the code references, there should be some fdxref files... they are created as part of the process...

Perhaps this is a rights issue.

can you check your access to the root of the c: drive?

I'm clutching at straws here - so if what I am saying is rubbish - sorry!

B-)

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[OldManOBIE]

No, not rubbish. You have no way of knowing...so you ask.

I have administrator rights to all workstations.

There are no FDXREF files anywhere. None on C: and none on any of the network drives. I went to a computer where the Code References works correctly and still no such file.

When the search completes, three files are created called x_ref.dbf, x_ref.cdx and x_ref.fpt, where x = the project name.

 

[GriffMG]

Doh, I think it is the documenting wizard that created the fdxref files!



Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[Dan Freeman]

What version(s) of Windows? If it's Vista or Win7 "have Admin rights" may not mean what you think it means.

But that begs a question: this used to work and now it doesn't. What changed? Did a Windows Update come along and whack a security setting? Did an obscure driver get updated and destabilize things?

What changed?

 

[OldManOBIE]

I'm using Windows 7.

I have full administrator rights.

Some call it Super Admin.

Here is a nice tip:

http://www.tech-forums.net/pc/f127/admin-rights-vista-windows-7-a-197772/

I did a system restore to a point where I knew it worked and still no luck.

I have come to accept this behavior and will live with it until I re-install Windows again.

I can't say nothing changed, because obviously something did. But I sure can't figure it out.

 

[TamarGranor]

Try rebuilding the Code References app from the source in the Tools\XSource hierarchy. Then, rename FoxRef.APP in your home directory and replace it with the newly build version. See if that makes a difference.

You might also try using the updated Code References tool from VFPX and see if that helps.

Tamar

 

[Dan Freeman]

Hmmm.... is anything showing up in the Windows event viewer? Applications that get abended are usually reported in there.

You haven't done any fiddling with the source for Code References, have you? (It would be brain-dead simple to *cause* what you're seeing, since we have the xbase source for the tool.)

Is the _FOXREF system variable pointed to the right app/location?

 

[OldManOBIE]

That was a good suggestion TamarGranor. I rebuilt the app, but still no luck. Then I tried several modifications....nothing worked.

I had already tried the Code References Beta from VFPX. I like some of the features, but the problem is still there.

And my _FOXREF points to the correct place.

 

[Olaf Doschke]

There are some other tables involved in code references than just the ones created at each pjx.

Maybe one of these tables is defect.

Foxref.dbf in HOME() is one. You can determine all involved tables from the sourcecode of foxref.pjx of course.

If it was admin rights, you'd get prompted or nothing would happen or you'd find files in C:\Users\YourAccount\AppData\Local\VirtualStore\Program Files\Microsoft Visual FoxPro 9\

Table defects could cause foxpro to quit.

Bye, Olaf.

 

[Dan Freeman]

Table defects could cause foxpro to quit.

Yes, but wouldn't you expect this on startup rather that when closing the app?

 

[Olaf Doschke]

True, but maybe only at closing the code references dialog it does a TABLEUPDATE() to the foxref.dbf or something else causing trouble.

It's an ODD error, dan. EVEN I agree

Taking a look into the source code running when code references closes might help finding out the reason.

Bye, Olaf.

 

[Dan Freeman]

Yes, it's odd! That's why perhaps looking at ALL sides of everything might give someone an idea.

 

[TamarGranor]

And if he's using his rebuilt version of the app, he can SET PATH appropriately, and then issue SYS(2030,1), so he can trace the code that runs on the way out.

Tamar