I'm relatively new to FileMaker and what I know comes from playing around and self-teaching with a book. I have never posted on a forum before, so I could be going about this all wrong (please let me know!).

Background:

I work for a university lab that gives questionnaire-type tests that results in numerical data. I'm trying to create a system so that the same data can be entered by two different people, with a "checking" system to validate that the data entered is the same (to circumvent entry error).

So, for one question on one test I have three fields: first entry, second entry, and a "check" field. The "check" field is based on an auto calculation: If (entry1 = entry2; entry1; "check").

I'm working with multiple tests which each have 200-400 questions, so I have a lot of fields.

Here's my problem:

Often, "0" is a data value. But, since FileMaker (I think) treats zero as a blank field, it doesn't work correctly with the check system. The only real issue with this is that if a "5" is wrongly entered in entry1, but the correct "0" is entered in entry2, the check field still uses the "5" as the correct value, and doesn't flag the discrepancy.

Any suggestions? I don't think there is any way to change FileMaker settings, but I haven't been able to come up with a straightforward function for this either.

Thank you!

Anna

I'm relatively new to FileMaker and what I know comes from playing around and self-teaching with a book. I have never posted on a forum before, so I could be going about this all wrong (please let me know!).

Background:

I work for a university lab that gives questionnaire-type tests that results in numerical data. I'm trying to create a system so that the same data can be entered by two different people, with a "checking" system to validate that the data entered is the same (to circumvent entry error).

So, for one question on one test I have three fields: first entry, second entry, and a "check" field. The "check" field is based on an auto calculation: If (entry1 = entry2; entry1; "check").

I'm working with multiple tests which each have 200-400 questions, so I have a lot of fields.

Anna

If you have a lot of fields you have a design problem. You should have a lot of (well, 200-400) RECORDS.

The questions should not be represented by fields, but by related records. Offhand I'd say you should have tables:

Tests

TestQuestions

Responders

ResponderAnswers

I agree with Bruce, but to address your immediate question, try turning that calc around:

If (entry1 <> entry2; "check" ; entry1 )

Make sure the "do not replace" auto-enter option is not checked.

Make sure the "do not replace" auto-enter option is not checked.

Even better, why not make it a calculation field? I don't see why switching the test to not equal should make any difference.

History shows this person posted the question and has not been back since; so we're just talking to ourselves.

Edited July 1, 200916 yr by Guest

...so we're just talking to ourselves

And your point? Some of the best learning episodes were discussions and debates amongst ourselves when the originator had left the building (along with Elvis). :wink2:

It's only been a couple of days.

I don't see why switching the test to not equal should make any difference.

It shouldn't make a difference, but I tested it and it did work one way but not the other.

With replace existing data being on? Can you post this file?

I must be losing it. I swear I got different results for those calcs yesterday but today they are returning equal results, as expected. Never mind!

I got it to work....what I thought was an error with zeros was actually just a wrong number in my calculation script. Thank you for your help, though.

(And you weren't just talking to yourself...I had looked at your replies each day, I just hadn't responded. Sorry.)

But have you looked into structuring this in a more effective way? The bazillion fields thing is just not the best way to do this.