Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Catching error information
Message
 
 
À
27/06/2018 09:59:58
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
01660874
Message ID:
01660910
Vues:
48
>>Also, regarding your approach of DEBUGOUT. I thought that DEBUGOUT only works when running the app from IDE, not when executing it as .EXE on customer system. Am I wrong about it?
>
>Then textmerge all the same info that went into debugout into a string, and log that string.

Ok. I agree, if I knew where I need to debug. As I states in the initial message of this thread, I am trying to capture all possible information during an error. I don't know where error may or may not occur. My customers do not always report error messages (for whatever reasons) but I would like to know. So that I can eliminate the problem in the next update or have a work around. DEBUGOUT or your approach of textmerge is useful if I was working on a specific problem.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform