Path to CLASS BROWSER

[tilltek]

When I fire up VFP9, SP2 I go to [Tools] and [Class Browser] is greyed out.
I go to [Tools] [Options] and put in the path to BROWSER.APP.
I hit [Set As Default]
OK, all is well, until next time I load VFP when I have to do it all over again.
What am I missing?
How do I make the path to BROWSER.APP stick?

 

[Mike Lewis]

First thing you should do is to include the full path when entering the filename in the dialogue. Something like:

c:\Programs Files\VFP\Browser.APP

(specify whichever path is appropriate on your system.)

If that doesn't solve it, check your registry entries. The class browser path is stored in:
HKEY_CURRENT_USER\Software\Microsoft\VisualFoxPro\XX\Options

(where XX is your VFP version number).

There should be an entry named _BUILDER which points to your class browser. If it's not there, insert it now. Again, be sure to include the full path.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[Mike Lewis]

By the way, I assume you remembered to click Set As Default in the Tools / Options dialogue?

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[tilltek]

Hi Mike,
Thanks for the input,
>Set As Default in the Tools / Options dialogue?
Done

>_BUILDER which points to your class browser
I have both _BUILDER and _BROWSER, both set to the correct path.
Still no joy

Maybe it's the rainy season here but I seem to be confused 10 or 20 times more than usual this last week or so.

 

[tilltek]

For what its worth, I have just changed [Tools] [Options] [Regional][DatFormat] to British (was American) and that stuck even after restarting Windows XP.
Is that a clue?

 

[Mike Lewis]

I have both _BUILDER and _BROWSER, both set to the correct path.

When I said _BUILDER, I meant _BROWSER of course. My mistake.

The only other thing I can suggest is that you write a startup script, containing this line:

_BROWSER = c:\Programs Files\VFP\Browser.APP
[code]

substituting the actual path to the APP file on your system.

You can run the startup program either from Tools / Options / File Locations / Startup Program, or from a Config.FPW file.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

[url=www.ml-consult.co.uk]Visual FoxPro tips, advice, training, consultancy[/url]
[url=www.customsoftware-edinburgh.co.uk]Custom software for your business[/url]

 

[tilltek]

Thanks Mike, yes, I sort of guessed I could do something like that.
But how does VFP load these settings?
Where are these paths, like the path to BROWSER.APP kept?
Are they only in the registry?
If so, why is VFP reading some but not others?
How can VFP possibly discard these settings?

What also concerns me is what other "quirks" are there waiting in the wings. Especially if I distribute a system.

 

[Mike Lewis]

Tilltek,

Yes, the setting is held in the registry (and only the registry, as far as I know), in this path:

HKEY_CURRENT_USER\Software\Microsoft\VisualFoxPro\XX\Options

(where XX is your VFP version number).

Why is VFP loading some and not others? I've no idea. Sorry.

As for other quirks .. well, no-one can claim that VFP is quirk-free, but the specific issue of the class browser shouldn't affect your distributed system. It's a design-time issue, so your users won't be aware or it.

Sorry I can't suggest anything else.

Mike



__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[tilltek]

Thanks again Mike.
I might try a re-install of VFP9

 

[tilltek]

SOLVED.....
Someone, no names no packdrill, had edited config.fp
I had entries like [_BROWSER = ""] and [RESOURCE = OFF].

It seems that this is the master setup file.

Thanks again for the input guys.