"The field cannot be modified until...."

[leonard]

I have created a simple relationship and selected an indexed text match field from the master and related files. When entering text in the related file, I get the following dialog box: "The field cannot be modified until 'blank' (field) is given a valid value." In the master field, entering data is problem free, however, input the same data in the related file match field and the dialog box opens and the data is erased. Also, I made certain no other files with the same names or parts are on the computer.

[oilman]

HI LEONARD

I have encounter this when i have tried to exit a record before completeinh the index field. The field you indexed on must be completed first before moving on.

Lionel

[leonard]

Thanks Oilman.

It happens after I have completed the data input and then hit the "Enter" key.

V. frustrating.

L.

[Ugo DI LUCA]

Hi,

As Lionel pointed out and as the error message is saying, you cannot modify the related record before you give a correct value...so that FM recognizes that there's a valid relationship.

Which means you need to exit the record in order to update the index. The simplier solution would be to include a "Exit Record" request, so that your record gets commited and validated.

BTW, is the data entered through a portal ?

Any way you can attach your file or test here...

[leonard]

Hi Ugo,

Your point, "exit the record in order to update the index" could be the snag; I'll be sure to try that. If it doesn't work, you'll find me back here. ;-) I didn't realize the need to exit for the validation process to take place. I thought it was activated automatically, like the auto save feature.

You noted that I should include an "Exit Record". That's a script step, yes? This problem occurred before I got to the scripting stage.

Ugo wrote: "BTW, is the data entered through a portal ?"

No, it was a matching field and two files.

Thanks again for the help.

[Ugo DI LUCA]

You certainly receive this message because the key from which you're trying to enter data doesn't have a value established.

Now, from what you said your relationship was, I have no clue why it wouldn't work. Are you sure these are both index fields ? Can't you set the field to be autoentered ?

Please post a clone of your file, as this would be easier for us to help you on this issue.

Or explain us what exactly you're attempting to do so that we can find another way around, as it seems you're not currently on the right track.

[Vaughan]

Weird things like this happen if the remote key is a stored calculation: FMP cannot enter a value into the key field (because it's a calc).

[Ugo DI LUCA]

Sure,

but "I have created a simple relationship and selected an indexed text match field from the master and related files."...

That's why I'm a bit concerned he received this message

[Bettina]

Here is what Leonard is talking about.

Take 2 files:

1. Master file

2. Secondary file

Create 2 same fields in each file:

Field 1: "Tag"

Field 2: "Name"

Establish a relationship in Secondary file to Master file.

Open Master file and insert the following for

"Tag": A

"Name": Daniel

Close file.

Open Secondary file.

Put "A" in for "Tag". Shouldn't "Daniel" appear for "Name" ?

Files in attached .sit

[Ugo DI LUCA]

No.

Check it back.

The field you're trying to enter is a related field from a self-relationship from Secondary file to Secondary file. There's therefore no valid relationship.

If you set the relationship from Secondary to Main on the Tag, then it would work, assuming the Name field uses this same relationship.

However, if you use a related field, then you wouldn't even access to the field as the relationship is not valid too.

Is that clear ?

This was also answered here .

[Bettina]

I rectified the error based on Ugo's comment, and it was still not working.

Then Leonard realized I was creating the relationship twice, making the "Tag" via the Master File and the "Name" via the Master File as well, instead of making the "Tag" via the secondary file and the "Name" via the Master file.

Now it works!

Thanks for all your help!!!

[Ugo DI LUCA]

Bettina said:

Then Leonard realized I was creating the relationship twice, making the "Tag" via the Master File and the "Name" via the Master File as well, instead of making the "Tag" via the secondary file and the "Name" via the Master file.

Glad you fixed it.

I'm not sure the structure you just described is the workable solution or Leonard's original structure though.

The Tag should just be an index field in the Secondary file. In his first post, Leonard said he had used an index text field in both file. In this case, it would surely have worked, which is why I was a bit worried.

Though, to give a complete answer on this issue and may be enlight you a bit more on relationships settings, there are several ways you could have the Name field filled according to the value in the Tag field.

From what you posted, and what you said, the Name field in your solution, in the Secondary file, is a related field from a relationship Tag::Tag.

This means that your Name field in the Secondary file is EMPTY.

In order to have the Name field be filled in the Secondary file, if this was your goal (and I think it is...if not, why would you ever create a field Name in the secondary file ?), then you'd need to either define the Name field as :

- a lookup field (targetting the value of the Name in the Master file by a relationship Secondary:Tag::Master:Tag)

- a calculated field using a formula along the lines of ::SecondaryToMain::Name.

I just hope this was clear.

[Bettina]

Ugo,

Hi.

It was interesting to note that Mike (whom you pointed me to) was having pretty much the same problem. Indeed it seems I now have a lookup field and it works, which is wonderful!

If by this:

"This means that your Name field in the Secondary file is EMPTY."

you mean, that it is empty until the Tag field is filled in, that is correct.

I never thought of using a calculated field with formula for this. Can you explain a little more, please?

And also, thank you very much for your help!

Bettina

[Ugo DI LUCA]

Bettina said:

If by this:

"This means that your Name field in the Secondary file is EMPTY."

you mean, that it is empty until the Tag field is filled in, that is correct.

What I meant was that, in your attached test files, you had formatted the Name field as a related field (in layout mode, the field looks like "::Name").

This means that you were using the value from the Main file, but the Name field in the Secondary file is Empty.

I never thought of using a calculated field with formula for this. Can you explain a little more, please?

Actually, when the calculation box opens, you'd just use the drop-down list up the field list, switch relationship and pick the Name field in the Main file, which would end in a formula in the box of type "RelationshipToMain::Name"

This would be an unstored calculation though.

[Bettina]

Ugo,

I greatly appreciate your help! I just started using filemaker, as is obvious...Thanks for the info. I am going to try the calculation solution you suggested and see how that works for me!