gmane.comp.lang.inug-4d.tech

Brad Perkins | 14 May 21:56

Tracing a Trigger

I know this has been discussed before, but my attempts searching the 
Archives couldn't find the answer.

I've placed a TRACE in some trigger code. I would expect this to bring 
up the trace window on the server, but I'm not seeing anything. I'm also 
not seeing any evidence that would indicate the trigger is stalled 
because of a TRACE.

I have restarted the 4D Client that would invoke the trigger.
I have restarted 4D Server.

I seem to recall that there was some special trick to get this to work. 
There may have also been some circumstances where it wouldn't work.

If it makes any difference I'm viewing the 4D Server via a RDC session?

4D Server 2003.7 running on Windows 2003 Server
4D Client 2008.7 running on Mac OS X Server (10.4.11)

Thanks,

Brad Perkins

**********************************************************************
The 4D v11 SQL Roadshow - coming to a city near you!
http://www.4D.com/roadshow/index.html

4th Dimension Internet Users Group (4D iNUG)
FAQ:  http://www.4d.com/support/faqnug.html
Archive:  http://dir.gmane.org/gmane.comp.lang.inug-4d.tech

(Continue reading)

headers

Matthias Schmidt | 15 May 02:03

Re: Tracing a Trigger

Am/On Wed, 14 May 2008 13:57:29 -0600 schrieb/wrote Brad Perkins:

>I know this has been discussed before, but my attempts searching the 
>Archives couldn't find the answer.
>
>I've placed a TRACE in some trigger code. I would expect this to bring 
>up the trace window on the server, but I'm not seeing anything. I'm also 
>not seeing any evidence that would indicate the trigger is stalled 
>because of a TRACE.
>
>I have restarted the 4D Client that would invoke the trigger.
>I have restarted 4D Server.
>
>I seem to recall that there was some special trick to get this to work. 
>There may have also been some circumstances where it wouldn't work.
>
>If it makes any difference I'm viewing the 4D Server via a RDC session?
>
>4D Server 2003.7 running on Windows 2003 Server
>4D Client 2008.7 running on Mac OS X Server (10.4.11)

imho the special trick you need is that the trigger runs at all.
What you write sounds it doesn't either run or the code never reaches
the trace point.

cheers,

Matthias

------------------------------------------------------------------------

(Continue reading)

headers

MIYAKO | 15 May 03:13

Re: Tracing a Trigger

Hello,

are the triggers for the specific Database Event turned on at the  
structure level?

miyako

On 2008/05/15, at 4:57, Brad Perkins wrote:

> I know this has been discussed before, but my attempts searching the  
> Archives couldn't find the answer.
>
> I've placed a TRACE in some trigger code. I would expect this to  
> bring up the trace window on the server, but I'm not seeing  
> anything. I'm also not seeing any evidence that would indicate the  
> trigger is stalled because of a TRACE.
>
> I have restarted the 4D Client that would invoke the trigger.
> I have restarted 4D Server.
>
> I seem to recall that there was some special trick to get this to  
> work. There may have also been some circumstances where it wouldn't  
> work.
>
> If it makes any difference I'm viewing the 4D Server via a RDC  
> session?
>
> 4D Server 2003.7 running on Windows 2003 Server
> 4D Client 2008.7 running on Mac OS X Server (10.4.11)
>

(Continue reading)

headers

B. Perkins | 15 May 05:07

Re: Tracing a Trigger


Miyako (and Matthias),

You both were on the right track. The table had a trigger method, but the
events had either been turned off or never enabled. Once I figured that out
I was able to debug them fine.

Thanks,

Brad

MIYAKO wrote:
> 
> Hello,
> 
> are the triggers for the specific Database Event turned on at the  
> structure level?
> 
> miyako
> 
> On 2008/05/15, at 4:57, Brad Perkins wrote:
> 
>> I know this has been discussed before, but my attempts searching the  
>> Archives couldn't find the answer.
>>
>> I've placed a TRACE in some trigger code. I would expect this to  
>> bring up the trace window on the server, but I'm not seeing  
>> anything. I'm also not seeing any evidence that would indicate the  
>> trigger is stalled because of a TRACE.
>>

(Continue reading)