Hi all,

Does anyone know of any issues related to copying and pasting groups of fields from one layout to another? Case in point..

I implemented an audit log in a table by using an auto-enter calculation for the log itself, and a calculation field for the content of the fields I wish to track for changes. The audit log works, no problem...the problem comes in when I select both fields in the Design Database dialog, copy and then past those fields in the Design Database dialog of a different table. They don't work! If I create a new auto-enter calc from scratch and paste the formula from the auto-enter that doesn't work, (and modify it for the new field name) the new auto-enter works just as expected.

Is there any known issue of copying and pasting groups of dependent fields from one table to another?

I'm a little leary of moving forward with this project until I can figure this one out, i.e. I don't want to waste my time developing a corrupt file.

Thanks in advance for your much appreciated help!

Take a look at this:

1.2.1. Fields that have auto-entered calculations depending on other fields no longer rely on field order creation for consistent results.

From: http://www.filemaker.com/support/updaters/fm8v2_mac.html

--sd

Hi Søren,

This occurred several days after I updated to 8.0v2. But there may be another contributing factor. The file I'm working on is accessed remotely, running on FM7 Server. Do you suppose that although I'm opening it with FM Dev 8.0v2 on my end, the issue may be caused by the file running on FM Server 7? :qwery:

copy and then past those fields in the Design Database dialog of a different table

Well my thought was that duping field def's inside the same solution - instead should be "globalized" via CF's to avoid redundance.

If you're right that the server treats it wrong, should you perhaps ensure to Copy in creation order instead of a perhaps sorted order.

Next issue I came to think of was that making linked calc's although being an autoenter, never have been endorsed ...quite similar to sum rounded numbers vs. rounding the sum alone.

But there to little to go on, in your thread - not that you're doing it too often, but we can't establish if some sort of denormalization actually is the source of the behaviour, we can't see if you're expecting fields to freshen on values a relation away etc. What is our guarantee that we not are solving a 24" error - even certified developers make them once and awhile!

--sd