VFP8 conflict with VS 2003?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: harvey akerman (hakerman_at_ix.netcom.com)
Date: 01/16/05 

Date: Sun, 16 Jan 2005 14:40:39 GMT

Since loading Visual Studio 2003 I have been unable to run debug in VFP
8 (the " debug do " as well "file open" menu options are grayed out).
Has anyone encountered this? ANy suggestions Thanks for any assistance.

Relevant Pages

  • Re: PARENT is not an object (Vfp bug?)
    ... VFP, menu 'Tools', Debug tab, Environment: Debug frame ... depending VFP version, debug in Foxpro frame was not that stable and gave Dr ... > my app working with the debugger. ...
    (microsoft.public.fox.programmer.exchange)
  • Wrong COM version for Interop Assembly
    ... I have a COM Interop assembly I'm accessing through VB and VFP. ... to debug the thing in VS.NET and it turns out I can't because it's loading V ... of the .NET framework. ... would have to be so for debugging I suppose. ...
    (microsoft.public.dotnet.framework.interop)
  • Re: Insert via another tables columns
    ... "foxproCharlie" wrote: ... >But any assistance in what I can do now?? ... the version of VFP that you have. ... Gene Wirchenko ...
    (microsoft.public.fox.programmer.exchange)
  • Debug on client machine (vfp 7)
    ... I need to debug an application on a client PC, where VFP is not present. ... have tried using messageboxes on strategic places in the code, ...
    (microsoft.public.fox.programmer.exchange)
  • Re: source error
    ... I've started to get the "source out of date" error when I trace or debug. ... I use vfp 6 sp5. ... How can I get rid of this error so I can debug again? ...
    (microsoft.public.fox.programmer.exchange)