Koen --

Glad to hear that you got Code References installed and working. Hope it was worth the effort.

Re: your question: would it be possible to make a method to save the correct location in the filelocation filed?:

That is exactly what the current install program is. That file location is stored in the registry, and the install program writes to the registry (you can open it and see it's a really brief program). I have no idea why that fails, or what the remedy might be.

Jim


>Hi,
>
>OK on my other pc (win7 Ultimate) I have installed your version 1.1 Beta.3 in a different subdirectory
>I hit install and got an OK
>
>When you than NOT change manualy in the Options dialog filelocation and instruct VFP to look in the correct directory for the Code Reference.app to be used it will still point to the earlier directory and in that case you, at least I found, in the loadresults method an error.
>Now changed in the options dialog. filelocations to the correct directory and all O.K. - it worked fine no errors. Thanks.
>
>I believe the error I have reported yesterday I encountered on my other win7 pc is to be related to i. a win7 unwillingness to make any changements in the c:\ directory unless you are working with ultimate and ii maybe also a wrong listing in the options dialog.
>
>Question: would it be possible to make a method to save the correct location in the filelocation filed?
>
>>Koen --
>>
>>In a message earlier today, I suggested the following:
>>
>>If you still get the error, all that the installation is really doing is changing where to find FoxRef.APP. In VFP, open the Options dialog, go to File Locations, and change 'Code References' to point to the new version.
>>
>>(Actually this is in your message, below) .... have you tried this?
>>
>>>James,
>>>I had installed the previous version in
>>>C:\Program Files\Microsoft Visual FoxPro 9\Codereference which is a subdirectory of Home() and not in the Home().
>>>It is also my system not to install any enhanced tools replacing the original VFP tools in the home() just make sure the file locations are correctly addressed in Tools->Options->File locations ->Location field
>>>the previous version worked fine that way.
>>>This revised version of Codereference gave me the error OLE 0x8002801d:DLL not registred
>>>I will now empty the Coderefence directory and reinstall the previous version as done before to confirm me that it works. Also will install the new version on my other Win7 configuration a config which does not have any restrictions to write anywhere.
>>>Will report back when everything done.
>>>Best regards,
>>>
>>>Koen
>>>
>>>
>>>>I think your problem may have had to do with choosing home() as the parent folder. I would never recommend that.
>>>>
>>>>For this release, as compared to the release in VFPx, the uninstall did not change. What changed was where the preferences (options) are stored -- now in a different place, so they do not interfere with the options in the default.
>>>>
>>>>>>That's an error I have never seen before, and may be related (somehow) to the something in Win7 that doesn't like you putting it in a folder off home(). I try some other folder ....
>>>>>>
>>>>>>If you still get the error, all that the installation is really doing is changing where to find FoxRef.APP. In VFP, open the Options dialog, go to File Locations, and change 'Code References' to point to the new version.
>>>>>>
>>>>>>Hoe this helps.
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>Jeff --
>>>>>>>>
>>>>>>>>If you would, please try the following link for FoxRef --
>>>>>>>>
>>>>>>>>http://dl.dropbox.com/u/1637031/FoxRef.Zip
>>>>>>>
>>>>>>>
>>>>>>>Jim hi,
>>>>>>>
>>>>>>>that version installing on my Win7 in directory subdirectory of Home() \Codereference and activating the install.prg will result into
>>>>>>>
>>>>>>>Error OLE 0x8002801d:DLL not registred.when activating the enhanced codereference tool.
>>>>>>>
>>>>>>>Regards,
>>>>>>>
>>>>>>>Koen
>>>>>>>
>>>>>>>
>>>>>>>P.S. enjoyed listning to your interview
>>>>>Jim.
>>>>>I had put it in the subdirectory of my home() [...\Microsoft Visual FoxPro 9] and it could very well be related to a Win7 problem. This was on a Win7 Professional. Why the your original version was installed and to be used without any remarks and this revised version not is not clear to me. What else did you change apart from the uninstall procedure?
>>>>>Will try this revised version on a Win7 Ultimate.
>>>>>regards,
>>>>>Koem