Thanks, but I found this already. At first, I didn't think this error was going into the log, but it turns out it was. Unfortunately, the key piece of information isn't available in VFP. (The line number of the calling program.) I was able to track it down, though, and the error is fixed.
Thanks,
Michelle
>Michelle,
>
>You dont need to create the memory dump to a file, as SBT already does this to syeelog.dbf file and you can take print out of a detailed Error report through System Manager. Print->System Logs->Error Logs, select the Report type as detail and any other criteria like Company number, application etc and you will find a detailed report reporting the :
>
>A. Error number , program, line number , Description of error.
>B. Program call strucutre.
>C. All the memory variables with their values when error occured.
>D. All the open files and there indexs etc.
>
>So you can find that report very handy.
>
>HTH
>
>Jeetu
Précédent
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement