Value List Problem -- To Large of a List -- Help

[Joseph31]

Hello all,

Setup:

Table 1: Name: "Main"

Fields for Table 1: "MainID", "FirstName", "LastName", "Address", "City", "Zip" & " Phone"

Table 2: Name: "Policies"

Fields for table 2: "RelMainID", "RecordID", "Seller"(Full Name)....etc....

Table 3: Name: "Seller"

Fields for table 3: "RecordID", "FirstName", "LastName", "FullName"(Calc) & "Address" Info.....

Relationships:

Main::MainID --> Policies::RelMainID

Seller::Seller_FullName --> Policies::Seller_FullName

Info:

There can be many polices per one Main page ie: Bob Smith has 3 polices all with different information

The Problem:

As you can see I have a seller field on the policy page...This field is a value list (made from another table called "Seller"). I have a drop down list that shows all pre-entered seller from the past. When you choose a pre-entered name it puts that name in the "Seller" field. When there is no name that you want you need to add a new record to the seller table.

Also, When you add a second policy to the main page and it has the same seller You have to scroll down a huge list to get the name into the Seller field.

Well, as you can imagine the list is getting very long.

Question:

1. Is there a way to make a script or something that will auto fill the seller field with the same information on the main page? Without selecting it from a list... (Maybe By Check Box that says "Same as Main"

2. Is there a way if there are two policies per main page -- to make the second seller have an option to be the same as the first seller. Maybe by checkbox again that says "Same as previous Seller".... But I still Need a way to add a new Seller in ither case if it is different

Please help.

Joseph

[Brian C]

Answer to your question: YES

You can accomplish this in one of 2 ways:

1) If what you mean by adding a 2nd policy means just adding a new record to the same database table, and you are adding the 2nd policy at the same time period that you created the first record, then you can use the auto-enter options under the define fields to use a value from the last record. This will allow you to create one record, and the next record created right after will have the same value as the previous record for a specific field.

------------

2) If you are not entering the records at the same time, then it will only be a little more complex:

Create a global field (example: "gTempStore")

This will be used to store a copy of the information that you want to have transferred from your Main Page.

SCRIPT:

(Make sure you are viewing the policy record that you want to copy in information for before you begin)

------

Enter Browse Mode

setfield[ gTempStore , FullName]

Create New Record/Request

setfield[ FullName, gTempStore]

-----

Hope this helps!

[Joseph31]

Thank you that works Great.

One more question: Now that I have that to work... This might be a little harder

I have a one to many relationship

Two tables:

"Main" & "Policies" there can be many policies per one main...

So if I am on the second Policy for that main and I want a script that will look at the first policy info and copy it to the second policy is there a way to do that. I tired looked a everything.

I tried set field but it just get confused with the record I am on... there has to be away to set the Rel_ID in a script so it looks at the correct policy?

Maybe not?

Joseph