last function not working

[julesw]

okay, this is driving me nuts, this was working perfectly well previously!

i have a field with the calculation last (last sub issue)

last sub issue is a repeating field created by a calculation involving another repeating field, which in turn is looked up in another table from a date entered in a third repeating field (for anyone who could follow all that!).

the lookup and calculations are all working, it is just the last, simplest bit - with the last function - that isnt. why would this happen, given it worked before? it must be something incredibly simple, but i cant think what it could be.

the field with the last calculation is a non-repeating field, with the calc result being a number, and it cannot store the calc results. so what else could it be?

please, save my sanity!

[transpower]

If you're attempting to apply a non-repeating field to a repeating field you need to use the Extend function.

[julesw]

where would i apply the extend function? surely not to the last function, the whole point of it is to work on repeating functions, and turn them into a non repeating value...

[-Queue-]

If you attach a sample of your files, we may be more helpful.

[julesw]

okay, here it is... good luck with it!

[julesw]

oops, sorry that didnt work! here it is attached...

dummy.zip

[-Queue-]

I don't know the account name and password.

Anyway, if your problem is due to related repetitions (relationships referencing repeating fields), then this is a bug for which we're stilll awaiting a patch.

[Ugo DI LUCA]

Hi JT,

The Last( ) used through a relationship work. What doesn't is the Value List trick.

[-Queue-]

True. This may be a refresh issue then. If you click into the 'last' calculation field, does the value update?

[julesw]

no it doesnt...

ok, ive attached the file again. you should be able to log in as guest and have full access priveleges.

dummy.zip

[-Queue-]

Remove the 'Do not store calculation results' check from the Storage Options for 'last sub issue'. It does not need to be unstored. Then your 'last of last issues' field will work. Note that it does not need to be unstored either.

[Ugo DI LUCA]

Hi,

Check your last issue, and even first issue calc fields options and uncheck the "do not store"

I hope this will not ruin other feature in your file, which I honestly didn't understood much...

Edited : Queue was there, and he probably has better eyes than mine, specially for scrowling your field list

[julesw]

oh THANK YOU THANK YOU THANK YOU!

funnily enough, i had tried to change the storage options of the 'last sub issue' field, and it wouldnt let me. but when i changed them for 'first sub issue' it then allowed it, and now it all works perfectly!

you have made my day...

j x