Heya Gene -
What Olaf said?
THIS was what I was alluding to back on my post to you on the 8th o April.
I'll repeat it here - just in case you missed it -
*----
Heya G Man -
there is a chance your boss can tell you where it failed, though,
Only a chance, not 100 percent, not foolproof , not guaranteed.
Load up vfp
load up debugger
launch the application from debugger
when it blows, click 'suspend'
you can MAYBE see the code in the debugger where it fails.
maybe....
Mondo Regards [Bill]
*----
So if you deliver an executable to your boss with the debug info thingie
checked, your boss can
SEE exactly where it blows in the debugger.
Regards [Bill]
--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.terrafox.net www.viasqlserver.net
"Olaf Doschke" <b2xhZi5kb3NjaGtlQHNldG1pY3MuZGU@[EMAIL PROTECTED]
> wrote in
message news:uZFFF4ijHHA.1244@[EMAIL PROTECTED]
> > text of the error line when running under the run-time. I have come
> > to the conclusion that there is no way to do it.
>
> I use Message(1) since 7 Years (even in VFP6),
> and if you compile with "Debug info" it does give
> you the source code line. Maybe you also need to
> uncheck "encrypted", haven't tested that.
>
> I call my error handler with:
> On Error Do ErrorHandling With Error( ), Message( ), Message(1),
Program( ),
> Lineno( ), Lineno(1)
>
> Additional I use AERROR() and ASTACKINFO() within the handler.
> And Astackinfo also returns the code, not just the line number, the help
> also tells you, that in column 6 of the ASTACKINFO result array you get
> source line contents. It works.
>
> Bye, Olaf.
>
>
|
