Thank you for your help, but since I'm a Rails programmer and don't know
anything about the OOo APIs, I don't have a clue what you mean :)
So you're saying that OOo is not capable of logging errors to the command
line? So I'll have to do some debugging like what I sometimes do with
JavaScript alert()'s, in a Language i don't know about? OK.
Can you then tell me how i open a file and write some text to it? and what
the heck is an "on Error" statement?

regards, Micha


2006/8/8, Andrew Douglas Pitonyak <[EMAIL PROTECTED]>:

First, create a small routine that accepts a single string and logs the
string to a file. Perhaps you coudl even add a time/date to the output.
Next, go to a few of the routines and have them call the log routine at
the start and end of the subroutine.
Now, you can at least try to see where the log messages stopped appearing.
When you think that you know the routine with the problem, you can add
an "On Error" statement and then write the line number and error number
to the file.

--
Andrew Pitonyak
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
My Book: http://www.hentzenwerke.com/catalog/oome.htm
Info:  http://www.pitonyak.org/oo.php
See Also: http://documentation.openoffice.org/HOW_TO/index.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Michael Siebert <[EMAIL PROTECTED]>

www.stellar-legends.de - Weltraum-Browsergame im Alpha-Stadium

Reply via email to