How can I trigger a script in calculation field?

Please help me!

You cannot trigger a script in a calculation field.

When posting a question, please describe why you feel you need this technique. I cannot offer an alternative solution since I have no information about what you are trying to achieve.

Plug-ins like EventScript can be triggered by calculations. (Before FM10 that was the only way to trigger scripts.)

Yes, Vaughan, that's true. I doubt that is what is needed here.

I attached a simple file that contains my problem

My_File.zip

Graph disorganized. Wrong field used for relation. Existing Archive::CustomerCode field seems to serve no purpose. See attached.

My_File.fp7.zip

Thanks for the arrangements but I see only details of the payment

Still sales details absent

Can you offer me some alternatives?

You'll need to explain clearly what you are trying to do. It is far from clear.

One basic problem is that you have an unstored customercode in Archive but that doesn't work, it should be a standard indexed field and not a calculaton.

I want to carry the data of the calculation field(Customer Code in Archive) to an idexed field. So I can see whole customer actions in the table of Selected_Archive.

I want to carry the data of the calculation field(Customer Code in Archive) to an idexed field. So I can see whole customer actions in the table of Selected_Archive.

What is the point of the calc? It doesn't belong there. The field CustomerCode must be a standard indexed field.

How is the archive record created? That's the process where you must set the CustomerCode field.

If I can trigger a script in any calculation field in Archive

It will cary CustomerCode data to the any standart indexed field.

So I can do relation

Sorry for my English

Perhaps you can, but generally if something like this needs to be done it means there is a problem with the data structure.

Generally there is a way of constructing relationships so that they work without having to resort to scripts.

It might be time to explain in detail what you went to achieve.

If I can trigger a script in any calculation field in Archive

It will cary CustomerCode data to the any standart indexed field.

So I can do relation

Sorry for my English

It's not the English; it's the programming logic.

It should not be a calculation field.

It should be a standard indexed field that is set as part of the archive record creation process.

It would be helpful to answer Vaughan's question.

Edited March 10, 201015 yr by Guest