>>Hi Cetin,
>>
>>I also would normally prefer using parameters but in this instance the value has to be available from within a trigger. So wouldn't it have to be declared public in the sproc anyway? My thinking was that, by doing it when the conneciton was opened, there would be virtually no disruption to existing code (i.e. no change in VFP and [hopefully] only in the one place in ASP)
>>Regards,
>>Viv
>
>I don't understand quite well why it has to be public. Triggers can have parameters.

Hi,
I guess I didn't meand 'has to'. But, as above:
(a) Dons triggers were already using a public variable
(b) A parameter approach would mean modifying every SP and every call to it from ASP (and from the existing VFP app) to pass in the username parameter.
My approach involved just adding one line of code in ASP.
Or am I missing something?
Regards,
Viv