I am creating a music cataloging database and I'm trying to copy data into a portaled field if there is data in another field. I would like to do this without a script, but I am am not having any success. I've attached the file to this post. Thanks in advance for your help!

Sam

Music_Collection_Test_Solution.fp7.zip

The only that I know of to accomplish this without a script is too insert the values on creation of the record in the portal.

I tried to do a lookup and still did not have any luck.

It isn't even something you should be doing.

You're trying to create redundant data. What is the point you perceive in doing this?

The reason I'm doing this is because some of the songs in collections don't always have the same theme or occasion. In the event that a collection does have the same theme and occasion, I do not want to have to enter it into every portal field. I also will add songs into the database that are not in a collection, and so I need a table to store themes and occasions.

I tried to do a lookup and still did not have any luck.

??

None of the fields are lookups in your example. As a matter of fact you don't even HAVE theme or occasion fields in your song table.

The reason I'm doing this is because some of the songs in collections don't always have the same theme or occasion. In the event that a collection does have the same theme and occasion, I do not want to have to enter it into every portal field. I also will add songs into the database that are not in a collection, and so I need a table to store themes and occasions.

You mean like this?

Music.zip

That is exactly what I want it to do, however the portal fields occasion and theme need to come from the occasion and theme tables, not the song table.

That is because the other part of the solution I'm have created which is not part of this file allows for multiple occasions and themes.

That is exactly what I want it to do, however the portal fields occasion and theme need to come from the occasion and theme tables, not the song table.

That is because the other part of the solution I'm have created which is not part of this file allows for multiple occasions and themes.

You'll need to keep explaining. That doesn't make any sense so far and you have 1:1 relations in your original file to the occasion/theme tables.

The file I posted on this forum is not the full solution fill I am creating. In my original file I have a song layout that allows me to enter individual songs and assign multipule occasions and themes through a portal. However when dealing with collections I think it is too confusing to have multiple occasions and themes. That is why I am going with 1:1 relationship on the collections layout only.

I appreciate your help.

The file I posted does everything you asked for. The separate 1:1 tables make no sense; they require you to create TWO realated records for no purpose that you have yet explained.

I've attached to this posting 2 jpg files that will clarify why I need a separate table for occasion and theme.

I've attached to this posting 2 jpg files that will clarify why I need a separate table for occasion and theme.

That does make it much clearer. In your previous post you said you needed a 1:1 relation from Song:Occasion, Song:Theme. Now you reveal that there is a 1:M relation. You really need to create THREE records when creating a new song within a collection, and you're only going to get this with scripted record creation. Doing it with scripts should be easy.

There are some folks, me included, who prefer not to use portals set up with auto-create and this is one good example of where it won't work.

Edited November 21, 200817 yr by Guest

Is there no way of creating a 1:1 relationship using the occasions and themes tables the Collections layout only, even though I am going with a 1:M relationship in the songs entry?

Edited November 24, 200817 yr by Guest