>> > registry entry that's been suggested. VFP works correctly on one
>> computer
>> > and not on the other, despite seemingly identical installations.
>>
>> Barbara, "seemingly" is just the word. Identical instalations simply
>> don't exist anymore ;)
>
>One of the things that I do on the side is manage a lab that is used for
>training. They have 25 PCs with "IDENTICAL" configurations and
>installations (down to the bit). How do I know that they're identical?
>Because it was designed that way.
>
>The first step is to have identical hardware.
>
>The second step is to create the exact contents of the hard disk that
>you want.
>
>The third step is to take an image of this disk and copy this image to
>the other machines. See www.ghostsoft.com for a program to do this (DOS
>based, but handles long filenames).
>
>This isn't really related to the initial thread, but it's still a cool
>piece of software. And it's great for 1) backing a machine up or 2)
>moving to a newer machine with a near identical hard disk.
>
>/Paul

That IS cool. When I was teaching earlier this month, the place where I taught had a similar setup so that all the students had exactly the same software. Hardware wasn't QUITE identical - a few monitors were different. The first day they came in at lunch, and in less than an hour they changed 13 machines from Win3.11 and VFP3 to Win95 and VFP5, including reformatting the hard disks.

Barbara