Function thing - threads

[charl99]

Hi,

My understanding is that if I read a record to memory, and I call a function that modify this record, it won't affect other users (or other records) called by other users?

To clarify, because Bruce never understand my questions

ie, I want to call a function and I want 3 parameters to be passed back, C_UWYear, C_InceptionDate and C_RenewalDate.  As I cannot get 3 parameters back unless I put them in a string, is it good enough to load the record, pass the information like Policy Number and Date of Loss to my function, where I then set these values and it will be changed when I get back from my function to NetTalk.

Thanks

Charl

[Ubaidullah]

Yes, it will change the record buffer. But, you need to set the session values for the fields after returning from the function. e.g.

   p_web.SSV( 'FIL:Field1', FIL:Field1)
   p_web.SSV( 'FIL:Field2', FIL:Field2)
   etc.

Regards,
Ubaidullah Nubar.

[Stu]

Charl,

Hi there.

As Ubaidullah mentioned, Session values are the bomb.

I'd be clearing them first, call you function where you set them, then after that use them.

[charl99]

Thanks guys.

These fields are background things needed for some calculations, ie not on the screen or anything, so I guess I don't have to worry about session values.

Cheers
Charl

[Stu]

Nooooo! Always worry about Session Values. Regardless of whether they are on the screen or not, Session Values are extremely important in the structure of a web system.

I'm sure Bruce could chime in with something clearer about now

[Bruce]

ha ha - well I've got Stu well trained <g>.
But "normal Clarion" doesn't go away, as long as you're on the same thread - and that's the key - being on the same thread.

So a block of code runs, as always, from top to bottom. Anything you do inside that block is good. Procedure calls, file buffers, it's all ok.

However _IF_ you want to use something in some other block of code, for example when the form opens you prime something, then do something with it when the form closes, well, there Session values are important because (and this is the really important bit to grasp) those two "actions" occur on different threads. A windows program puts all the Form interaction on one thread, the web doesn't.

Cheers
Bruce