Angus Cameron

To start with you will need to store the call date on each record. Presumably you will store just the last date called. There will be two additional calculations: Day_called [DayOfYear(Call Date)], Week_called [WeekOfYear (Call Date)]. You don't say how you are going to specify the day and week number at the top. If you are happy to summarise the totals to show on only Warm calls made on the same day as the record you are viewing then it can be a simple self join: Call outcome to Call outcome and DayOfYear to DayOfYear. If you want to be able to specify a day/week you might create some global fields as the parents of the join: The fields being Call_Quality (Global, contents "Warm"), Date_specified (Global), Date_specified_Day (Global calc), Date_specified_week(Global calc). Then add the first two Globals to the top of the layout and create the relationships Call_Quality to Call Outcome AND Date_specified_Day to Day_Called. Same for Date_specified_week to Week_called. Call the relationships: Data_Data_DayOfYear and Data_Data_WeekOfYear Finally, you have two more calculation fields: Count( Data_Data_DayOfYear::CallQuality )& Count( Data_Data_WeekOfYear::CallQuality ) These will accumulate totals for the two relationships.

Has anybody experienced a failure within a new calculation of the "Evaluate this calculation from the context of.... " list to update with all appropriate relationships in the relationship graph. My file which started life in FM5 lost its reference to the main table recently, necessitating all new calculations to be copied from a previous calculation, which still had the full list, and then amended. I have partially overcome this problem by deleting the two relationships that remained in the list. Somehow this forced the main table to reappear in any new calculations and a couple of others popped up as well. However, I am still missing about 20 that have been created over time. I would rather not delete these 20 as well and reinstate them because this appears to corrupt relationships / lookups in other files which use this file, not necessarily these relationships. There must be an underlying table that is being referenced and has become corrupted. Any ideas how I might force it to behave, please?

Further to my comments above, I have realised that if I open files in the conventional way they appear in the Window / File List. I have opened up to 10 files successfully. However, if I use a script with a series of Open File steps (not minimised) the list stops after two files and sometimes after only one.I have tried recovering the third file in the series but that makes no difference. I have also tried a "refresh window" script step between each open but that also does not help.The files all open but without a reference in either of the two lists: Open or Hidden.

When I open a series of files I find that the majority are neither listed in the Window - Open Files listing nor the Window / Show Window (hidden files) listing. The only practical way to navigate between files is to minimise the one in view, select the other file I need and maximise it. Surely there must be an easier way than that? I wonder whether this is an error on my system or a shortcoming of Filemaker 9 Advanced?

Thank you very much, that solves my problem. I have only recently graduated from fp5 and need to get used to the conditional relationship facility in fp7. I am sure that the same technique will help me elsewhere.

I have a manufacturing inventory database that stores usage and purchase quantities on random Transaction Dates up to a year from now. I have a series of calculation fields which allow me to determine on what date for a given Stock Code the quantity in inventory turns negative, that is usage exceeds purchases. Because the calculation is quite processor intensive, but I need it to be real time data, I am trying to limit the calculated transactions to only those within the next 90 days. To do so I have an indexed field "Stock Code Date", based on the Transaction Date, which contains the Stock Code for transactions up to 90 days away but becomes blank thereafter. As a result the relationship that I have created between the Master Inventory Stock Code Record and "Stock Code Date" only identifies near term records and ignores those more than 90 days away. My problem is that for the relationship to work the "Stock Code Date" must be indexed. But an indexed field does not update based on a change in the current date. I don't want to have to manually un-index and re-index the field every day. Is there a way in which I can automate this process, please?