Hi Folks,
For development purposes, we have a setup to trigger the foxpro debugger to pop up when testing our web pages.
This works just fine on Windows 7, but with windows 10, I can see the new vfp 9 instance inside the task manager, but the debugger display doesn't pop up on the screen to help point me to where the error is.
oVfp = CREATEOBJECT("VisualFoxPro.Application.9")
ovfp.docmd("_screen.WindowState = 1")
ovfp.docmd("_screen.visible = .t.")
ovfp.top = 0
&& to trigger the debugger
cStr = "2"
IF cStr = 2 && << This will trigger the debugger to pop up
cStr = "3"
ENDIF
ovfp.quit()
RELEASE ovfp
If I run this directly inside VFP9, it works fine, but if I call the .FXP (let's call it test_screen.fxp) from my .ASP web page (see below), the vfp9.exe shows up in task manager, but lingers there and the the web page just spins until it times out.
This is what the .ASP looks like:
<%@ LANGUAGE="VBSCRIPT"%>
<%
Set lo = Server.CreateObject("aspfox.aspfox")
Response.Write( lo.runFXP("test_screen","C:\inetpub\ Set lo = Nothing
%>
I'm unsure how to trace the vfp9 and see what it's doing and where it's hung up on. I've tried disabling UAC, increased permissions, set vfp9 to run as administrator, and disabled windows defender, but I cannot seem to figure out what on Windows 10 is keeping the debugger from popping up on my screen.
I appreciate any insights.
Thank you,
David
For development purposes, we have a setup to trigger the foxpro debugger to pop up when testing our web pages.
This works just fine on Windows 7, but with windows 10, I can see the new vfp 9 instance inside the task manager, but the debugger display doesn't pop up on the screen to help point me to where the error is.
oVfp = CREATEOBJECT("VisualFoxPro.Application.9")
ovfp.docmd("_screen.WindowState = 1")
ovfp.docmd("_screen.visible = .t.")
ovfp.top = 0
&& to trigger the debugger
cStr = "2"
IF cStr = 2 && << This will trigger the debugger to pop up
cStr = "3"
ENDIF
ovfp.quit()
RELEASE ovfp
If I run this directly inside VFP9, it works fine, but if I call the .FXP (let's call it test_screen.fxp) from my .ASP web page (see below), the vfp9.exe shows up in task manager, but lingers there and the the web page just spins until it times out.
This is what the .ASP looks like:
<%@ LANGUAGE="VBSCRIPT"%>
<%
Set lo = Server.CreateObject("aspfox.aspfox")
Response.Write( lo.runFXP("test_screen","C:\inetpub\ Set lo = Nothing
%>
I'm unsure how to trace the vfp9 and see what it's doing and where it's hung up on. I've tried disabling UAC, increased permissions, set vfp9 to run as administrator, and disabled windows defender, but I cannot seem to figure out what on Windows 10 is keeping the debugger from popping up on my screen.
I appreciate any insights.
Thank you,
David