I have a file that calculates commissions based on related data in two other tables in a different file. We just discovered that the calculation is not accurate unless the related file is actually open in the background on the same computer as the first file where the calculation field exists. This is in Filemaker 9 on Server 9.
I also had the strange situation today of updating a layout and revising a calculation on the server file, then having the calculation work correctly on my computer connected to the server, but another computer hooked to the same server showed only the prior, incorrect calculation result. (In this case all the tables referred to were part of the same file and permissions were set to the same permissions group on both computers.) The calculation is a related field showing in a portal, but moving off the record on my computer, moving to a different table layout, moving to a different record on the other computer, and changing a variable that was part of the portal link (so that the calculation would refer to info from different related records) did not fix the error. We were finally able to get the calculation working on the second machine by closing Filemaker and restarting it, then reopening the file on the machine that had been showing the incorrect calculation result. I am wondering if these are signs our database is getting unstable, or what might cause such problems. This is the first time I have seen an update I have made not show up immediately on another computer connected to the server-- and I am often updating and changing layouts and calculations in real time during meetings, based on input and requests. Prior to this the revisions have always appeared right away on everyone else's computers, so this lack of immediate change seemed really odd. Any diagnoses, thoughts, or possible explanations? Thanks, Sue
