Indexed calculation field not steady when defining

[Logixx]

Hello.

Here is a strange FP5.5 feature I'd like to fix with the help of you all.

I have a calculation looking like this:

Case(Statut_patient = "GR" and Type_patient = "Ambulatoire",Code_GR,Statut_patient = "GR" and Type_patient = "Hospitalis

[-Queue-]

The fields you're referencing must be stored as well. Check that neither field is unstored or has the 'Automatically turn on indexing if needed' box unchecked.

[Logixx]

Thank you for your post.

All the referenced fields are stored and indexed. Shouldn't they be, Filemaker would not allow for storing the referencing field in the dialog box.

I wonder why FM allow for storing and then turn it back off as soon as the dialog is closed...??

[-Queue-]

Can you attach a copy or clone of your file?

[Logixx]

Here are the files. As raw as possible.

Open the fields definition dialog in file Soins.

I need to involve the calculation Calc_ID_session_TP in a relationship, so it is necessary to store it and the referenced field Code_attestable as well.

If I turn them to stored, FM turns them unstored when closing the dialog...

May come from kind of 'circular calculation' (I must still investigate). Or maybe any other misconception of mine...

But why the hell does FM first accept the storing option?

[Lee Smith]

Your calculation Calc_ID_session_TP is based partially on ID_patient, which is based on a relationship, (ID_session::ID_patient). The ID_session::ID_patient can't be stored do to the the relationship, therefore Calc_ID_session_TP

HTH

Lee

[Logixx]

Lee,

Based on what you wrote, I just turned ID_patient into a look-up via ID_session::ID_session, indexed it, and everything works fine.

Thank you for part one of the explanation!

Now part two remains: why does FM first accept the storing (which is quite impossible) instead of graying the option (and/or alerting) as it usually does?

One more terrible 'feature'?

[Lee Smith]

Hi Logixx,

I would deduce that it can't check this until you close the Define Field box. Probably because, it doesn't know what your final calculation will be until you close the box (i.e. you could remove this field prior to closing the box.

HTH

Lee