Craig,
> -Original Message-
> From: [EMAIL PROTECTED] On Behalf Of Craig Bennett
> Sent: Thursday, 11 May 2006 16:03
> To: u2-users@listserver.u2ug.org
> Subject: Re: Fw: [U2] UniData logging of BASIC Runtime errors
[snip]
> wouldn't it be great if UV and UD logged to syslog (every plat
Mike,
Yes, Yes, YES!
CALL OSEventLog(Category, Type, EventID, DescriptionText)
surely that one is easy using GCI? If you really want it
(excuse the unix version, can error logging from C be that much harder
in windows?)
#include
void OSEventLog(int priority, char* message){
syslog(prior
Well, for Windows platforms, you can do something like this (this is from
ECL, but with a tiny bit of code...):
:! eventcreate /t information /id 999 /l System /so MyModule /d "Error Test"
/t = ERROR | WARNING | INFORMATION
/id = Event ID
/l (lowercase L) = APPLICATION OR SYSTEM
/so = SourceName
ED] On Behalf Of
> James Canale, Jr.
> Sent: Friday, 12 May 2006 05:28
> To: u2-users@listserver.u2ug.org
> Subject: RE: Fw: [U2] Unidata logging of BASIC Runtime errors
{Unclassified}
>
> Well, for Windows platforms, you can do something like this
> (this is from ECL, but wi
Mike,
But actually, if you're on UV 10.1 you can use the new GCI function
"UVRunCommand" [see Issue Number 5616 in the Release Notes] even in
transaction State.
Gee, another reason to upgrade! :-)
Or you could call the windows api functions directly from GCI.
I'd find you the reference in O'
: RE: Fw: [U2] Unidata logging of BASIC Runtime errors
{Unclassified}
Thanks, Jim
That's brilliant ... Except it doesn't work in Transaction State because
you can't do a "DOS /c ...", you get a 'Verb "DOS" illegal when a
transaction is active' error. Dar
Thanks Phil,
> -Original Message-
> From: [EMAIL PROTECTED] On Behalf Of phil walker
> Sent: Friday, 12 May 2006 19:37
> To: u2-users@listserver.u2ug.org
> Subject: RE: Fw: [U2] UniData logging of BASIC Runtime errors
> {Unclassified}
>
> Mike,
>
> You c
