Hello All,

I have a portal that i use to verify products with another portal. When this order is verified it should automatically update the calculation in the verify table and output verified in the current layout. It does not automatically update. The only way for this update to occur is if I commit the record by clicking outside of the portal.

The only thing that drives me nuts about this, is that it works correctly in FM6 by automatically updating the calculation without having to commit the record.

Any help with this one would save me from going nuts.

The thing that changed with FM7 is the ownership of the record in an multiuser environment and the inclusion of a commit command.

But we would need to see the calc that doesn't update, to suggest a way to deal with these changes, chances are that it can be done differently, by being moved to the other table in the relationship.

--sd

Ok I am going to upload the file with a sample record. The file will open into the order scanning layout, the order number is 1234, enter that then do a command or ctrl 1 to execute the first script to go into the verification layout.

next you will click in the right portal first line and enter 12345612345 for the item number then tab to go to the next line in portal(this invoice should have that item 3 times).

Enter the item 3 times by tabing after you enter the item number. After you have completed the three scans the top blue and middle red should say valid but they do not(They still say Error Check Products) until you commit the record.

Someone please help as this is driving me nuts.

_Clone.fp7.zip

I have a little trouble getting the idea... have you tried to include a commit record step at the spot where you usually click outside the portal.

Then to the methodology applied, there is no apparent need to tie all TO together in one single spiderweb, make a thread for each layout, because you make it almost imposible for a stranger to the process to debug it.

Now scripted validations means that you apparently have learned something from other tools, which have made you ignore that filemaker have native validations ...where you can see if a value is member of a valuelist or even more complexly fulfills a calculated equation.

Now you must also realize that the Count( function works either on a list of fields, a repeating field or over a relation. This means that the way you use Count( is not particular better than Duke(

...well not quite! not IsEmpty( perform similar.

So by and large should you try to get rid of some of methods used somewhere else, and investigate in help how the syntax is for the various functions. At least try to explain what is the idea behind this:

If(Count(Valid) ≠ Count(Invoice);"Error "Check Products"";"Valid")

--sd