Many of the VFP tools you might have customized keep their settings in DBFs. For example, the primary tools I use are Intellisense, the Environment Manager in the Task Pane and the Toolbox. All these DBFs that can be backed up and restored in a migration. Also, all the stuff you see in Tools->Options live in the registry and can be exported and imported.

For Intellisense, I keep this little reminder around:

TEXT

RUN this command to save custom intellisense records from your Foxcode table

*!* SELECT * FROM (_FoxCode) WHERE Type = 'U' INTO TABLE <place you want to save your stuff>

RUN this command to restore your saved Intellisense commands

*!* INSERT INTO (_FoxCode) SELECT * FROM <place you saved your stuff>

ENDTEXT

Personally I moved my FoxCode and Toolbox tables out of the default location VFP puts them long ago so they are pretty easy to find. The Environment Manager tends to be buried in your Windows roaming profile folder and its table does not exist until you save an environment for the first time.

--

rk

-----Original Message-----

From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche

Sent: Wednesday, December 17, 2014 7:16 AM

To: profoxtech@leafe.com

Subject: Re: Moving VFP9 sp2

I used the Microsoft "Easy Transfer Wizard" to move the contents of a broken (LCD) laptop to a new one just last week. It was neither easy nor such a great transfer. After hours of fussing with network connections (with totally lame error messages) I was able to connect. File transfers were successful but really slow over a high-speed connection. "1 minute remaining" hung on the screen for the last half-hour. It provided a list of executables to be installed once it was done, including VFP. Many settings came over; some didn't, so you still need to do a full review of all your software, daily use and once-in-a-blue-moon.

I think this is probably the best you can do, as the final configuration of the Registry is not something any software (nor any person!) can predict, as every install, de-install and update changes the Registry.

If I have to do it again, I'd snapshot the file system and simply reinstall all the software.

Dan Freeman had it right, years ago: flatten the OS and reinstall what you need.

On Wed, Dec 17, 2014 at 4:57 AM, AndyHC <jarndice@gmail.com> wrote:

>

> Hi,

> I am in the process of partly migrating to a 'new' PC (Win7).

> I have the msdn cd for vfp but I'm trying to save the hassle of a full

> install on the new m/c - has anyone [success]fully moved VFP9 sp2

> (+Sedna) from one m/c to another (exe's dll's registry etc.) - or at

> least 'slipstreamed' the exe's/ dll's?

>

> Any suggestions welcome

>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/CY1PR10MB0218CA87FB73AB37FB022B2CD26D0@CY1PR10MB0218.namprd10.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.