.

I think you could use a DirectSQL Active Link.

Regards
Alfredo Avendano
Caracas - Venezuela

--- Darwin Palma wrote:
> I don't see any real solution for this, as it is
> explained. Clearing the
> change flag could produce bigger problems. If the
> user has made changes
> before pressing the button, he would be unable to
> save them unless he
> changes something else.
> Another approach would be set the field to not alter
> the Change Flag, but
> again, there's no guarantee that the value will be
> saved.
> If you keep pushing the values to the database, you
> will ALWAYS get the
> message you are getting.
>
> The only thing I can think of right now is to keep
> the statistics in a
> separate form. May be saving the case ID and the
> user ID. It could help you
> since it will allow you to define as many actions as
> you want to log,
> without defining that many fields. If you like the
> idea I could elaborate
> more.
>
> Darwin
>
> -----Original Message-----
> From: Fondse, Theo
> [mailto:Theo.Fondse@ARS.SMC.SIEMENS.CO.ZA]
> Sent: Tuesday, May 27, 2003 07:53 AM
> To: ARSLIST@ARSLIST.ORG
> Subject: Re: I push it real good.
> Importance: High
>
>
> **
> Hi Morgan!
>
> It seems to me that what you need to do is to reset
> the change flag of the
> ticket after you do your set fields.
>
> I have attached a generic macro that does this for
> you.
> It has parameters you need to set in your run macro
> action:
> $Action$: 3
> $SchemaName$: $SCHEMA$
> $ServerName$: $SERVER$
>
>
>
> Best Regards,
> Theo J. Fondse
> Remedy Developer
> Siemens Business Services
>
> Telephone: +27 11 652 7477
> Mobile: +27 83 773 3075
> e-Mail: theo.fondse@ars.smc.siemens.co.za
> Web: http://www.siemens.co.za/
>
>
===========================================================================
>
> -----Original Message-----
> From: Morgan Stahl [mailto:morgan.stahl@VV.SE]
> Sent: Tuesday, May 27, 2003 10:22 AM
> To: ARSLIST@ARSLIST.ORG
> Subject: I push it real good.
>
>
> **
>
> Hi all.
>
> From a request I want to be able to push a value to
> the same request (this
> for adding some statistics about the users action,
> without the users
> knowledge). I could use set field but then the user
> needs to save the
> request (I could do it by commit, but then it could
> save some changes the
> user didn't want to save). Now to the problem, when
> I use the push and then
> the user wants to change this request he gets a
> dialog that tells him that a
> user has made changes to the request and by saving
> he would discard these
> changes.
>
> So my question is: how can I push a value the same
> request that the Active
> link was activated in, and not get a dialog when the
> user tries to save
> his/hers changes.
>
> This scenario comes from a request where I have a
> button that should only be
> pressed once, and as I stated earlier I don't want
> the user to have to save
> after he presses the button, but then I can't be
> certain that the user
> doesn't do changes and tries to save the request...
>
> Ok I tried my best to discribe this problem, I hope
> at least some of you
> understood my problem.
>
> Regards Morgan
>
>