I had run into this issue several years ago. A VFP repair install did NOT fix it, nor did a complete uninstall/reinstall fix it. Doug's tip took care of it, that's why I knew of it.
Fred On Sun, Jul 26, 2015 at 7:28 AM, Kurt @ VR-FX <[email protected]> wrote: > If U ask me - this GUID this thing is a moot argument - since Fred already > pointed to Doug Hennings explanation - which seems to be what is probably > happening. Although - Doug's suggestion on the Fix is More cumbersome than > the one that they did at my day job - merely doing a VFP Repair... > > -K- > > On 7/26/2015 7:49 AM, Ted Roche wrote: > >> On Sun, Jul 26, 2015 at 3:36 AM, Alan Bourke <[email protected]> >> wrote: >> >>> Each person on earth would have to own 600 million GUIDs for there to be >>> a 50% chance of a collision. >>> >>> OTOH, someone messes up their Registry every day. >> >> While I like Ken's theory, it's far more likely someone transposed a >> key while writing a registry file, or set up some strange dependency >> that means every time some obscure OLE control is invoked, it looks >> for some library that links to another set of keys that points to a >> feature that somehow is blamed on the VFP install. >> >> Dependency Hell isn't just a Microsoft thing, but they do it more >> obscurely than anyone else. >> [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] 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/CAJCBksqGKVk0MJDZf5dH4iHQe3xuQwNhFx1ap-Qx6zwMaK-=a...@mail.gmail.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.
