Good method, Karen. I use a varchar and append the whole log file into
it. Your method of appending each entry sounds better.
Albert
On 8/24/2014 10:19 AM, Karen Tellef wrote:
I do the same kind of thing, a log file. But if you don't want the
log file to
constantly append because you're worried about the size, or you're worried
that the file might get overwritten, you can also create a log TABLE and
append entries to the table with a unique number so you can identify a
single process and a datetime stamp. You just have to remember
to clean out the table periodically, maybe in the startup file based
on the
datetime stamp.
And also remember to identify the workstation that is running the
procedure.
One time we were able to identify a particular workstation as having the
only problem, and found a bad network card.
Karen
-----Original Message-----
From: Albert Berry <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Sun, Aug 24, 2014 11:01 am
Subject: [RBASE-L] - RE: Capturing filename and line number
I have used Tony's system on occasion to log occurrences. At the top and
bottom of each sub module, I would put a line such as:
OUTPUT LogFile.txt APPEND
WRITE "Start Name check procedure", .#NOW
OUTPUT SCREEN
<do the name check procedure here>
OUTPUT LogFile.txt APPEND
WRITE "Completed Name Check Procedure",.#NOW
OUTPUT SCREEN
This would create a log file. In the morning, if a check of the last
entry in the file showed the last procedure was completed, no problem,
otherwise the last entry would show the start of the sub module, and not
the end, letting me know which piece broke.
Albert
On 8/24/2014 1:54 AM, Tony IJntema wrote:
> Dennis,
>
> Years ago I also have created a huge daily process, which has to be completed
in one go.
> In this particular case I have built in some statements which add a row to a
log table mentioning which part of the process has been started and / or
completed. Together with a date and time stamp.
> It enables you to find out in which part of the process problems occur.
>
> Another possiblity is to make use of the ON ERROR command
> Have a look at the help for this particular command
>
> Tony
>
>
> -----Original Message-----
> From:[email protected] <mailto:[email protected]> [mailto:[email protected]
<mailto:[email protected]?>] On Behalf Of Dennis McGrath
> Sent: vrijdag 22 augustus 2014 23:01
> To: RBASE-L Mailing List
> Subject: [RBASE-L] - Capturing filename and line number
>
> Is there any way to capture the executing file name and line number of a
command when an error occurs so we can pop up the info in a pause command?
>
> We have a process that runs for 45 minutes before failing. There are a huge
number of code files involved.
>
>
>
>
> [cid:[email protected]
<mailto:[email protected]>]<http://www.qmiusa.com/>
>
> Dennis McGrath
> Software Developer
> Email:[email protected] <mailto:[email protected]><mailto:[email protected]
<mailto:[email protected]?>>
> Toll Free: 800-446-2500
> International: 01 630-529-7111
> Extension: 1026
> Direct: 630-980-8461
>
>www.qmiusa.com<http://www.qmiusa.com
<http://www.qmiusa.com%3Chttp://www.qmiusa.com>>
>
>
>
>
> .
> ________________________________
> This email may contain material that is confidential, privileged and/or
attorney work product for the sole use of the intended recipient. Any review,
reliance or distribution by others or forwarding without express permission is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies
>
>
>
