Left ( Actions::Discipline ; 1 ) & Actions:: Item#
set the new field to be an unstored calc
Left (First Field Name ; 1) & "." & Second Field Name
make sure the calc is unstored and the calculation result is text.
highly reccomend that you look in the help file and get really familiar with the text functions
along with memorizing the word seperators
these are bread and butter functions and mastering them will save you alot of headaches
make sure the calc is unstored
Both correct answers. Awesome, that is the fastest I have learned something new...Very very happy.
Thank you very much I will definitely look in the Filemaker help a learn the text functions. I really appreciate this advise.
I could not find anything to select that it was unsorted but it worked anyway.
The 'unstored calculation' option is under 'Storage Options' when you set up the field - IF you make the field a 'calculation' type. It's actually a checkbox labeled "Do not store calculation results...recalculate when needed".
If the field is of 'Text' type, you won't specifically have this option. However, I would actually suggest that you do make it a 'Text' field, and define it to have an 'Auto-Enter calculation' (under 'Options' -> 'Auto-Enter' for that field). Use the same calculation as described above as the auto-enter calculation definition.
Since it sounds like all of the fields you are using to create this calculation are from the same table (and this calculation field will also be living in that same table), you will get performance gains. Instead of having to recalculate the new string all the time (which is what an 'unstored calculation' has to do), it will only calculate the new string once - whenever any of the other fields are changed. So if the 'Discipline' or 'Item#' are changed, then this new auto-enter calculation will update with the new information. From then on it is stored/static information which is much faster to reference when shown on layouts, used in relationships, summaries, etc.
Here's where you can set up the auto-enter calculation for a Text field:
Oh! And be sure to DESELECT the 'Do not replace existing value of field (if any)' checkbox - otherwise this field won't ever change if the other two fields are changed. This is kind of the same as checking 'unstored' for a field that is a Calculation field-type.
Yes, sorry my brain say unsorted because I have been creating sorting scripts all morning.....lol
thank you and i will do the auto enter method.
Many thanks to you all you have all been a life saver for me...and probably a job saver too.