NetTalk Central

Author Topic: Run code from Server Side  (Read 3140 times)

rupertvz

  • Sr. Member
  • ****
  • Posts: 326
    • View Profile
    • Email
Run code from Server Side
« on: February 15, 2012, 11:23:33 PM »
Hi Guys,

There is some code that I'd like to add to the server-side window of my web-server app.
Thus, adding it to the web-server procedure.

How do I built-in a trigger from the web-page to 'action' the code inserted in the web-server procedure?

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: Run code from Server Side
« Reply #1 on: February 16, 2012, 12:05:10 AM »
what sort of trigger do you want? a button on a form maybe?

cheers
Bruce

rupertvz

  • Sr. Member
  • ****
  • Posts: 326
    • View Profile
    • Email
Re: Run code from Server Side
« Reply #2 on: February 16, 2012, 12:40:29 AM »
Hi Bruce,

I think the best way is to code the "trigger" in the post-insert, start embed of the form.

Thus, when the record is inserted, it will action the code on the server-side.

Regards
Rupert

rupertvz

  • Sr. Member
  • ****
  • Posts: 326
    • View Profile
    • Email
Re: Run code from Server Side
« Reply #3 on: February 17, 2012, 01:19:12 AM »
Hi Bruce,

Is it possible to put a "timer event" on the server side procedure to monitor for a trigger?
How do I pass a value from a session variable to the server side "timer event" to trigger the event?

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: Run code from Server Side
« Reply #4 on: February 17, 2012, 03:10:59 AM »
>> I think the best way is to code the "trigger" in the post-insert, start embed of the form.

ok, so make a call there, or start a thread or whatever you like. so what's the question?

>> Is it possible to put a "timer event" on the server side procedure to monitor for a trigger?
>> How do I pass a value from a session variable to the server side "timer event" to trigger the event?

sounds to me like you're trying to make something really simply into something really complicated. why not just call the procedure from the Post-Insert embed point? Start a thread even if it's gonna take a long time.

cheers
Bruce