Explanation Please

[dharkin]

Can someone explain this procedure to me. I always use lookups.

This is the post number Post#268523 I don't understand how the fields are stacked and what scripts are used to make this happen.

When you click in the client field to add a new record the field arrow appears and it will not in any attempt I make.

I copied and pasted the fields and it still would not do what the client field would do

Can someone explain this step by step?

Thanks in advance

Edited December 2, 2007 by Guest

[Genx]

Firstly there is a script attached to 1 of the fields... which means that just copying the fields won't do it to another db and hoping it will work won't make it work - that being said, i'm not sure the script is necessary. Take a better look at the sample file.

The stacking has to do with the order the fields are placed on the layout - and by that i mean the "arrange" options - bring to front / back. If you put one field in front of the other, and disable entry into the front field, you can actually access the back field directly by clicking on the front field...

So say you had:

ID - Rear Field;

Clients::Name - Front Field;

Disable entry in browse mode in the front field, attach a value list to the rear id field and place the front field on top of the Rear Field - you should now be able to click the Clients::Name field (or appear to) on the layout, select an id and have it update the Clients::name field.

If that's not your question well I didn't really both to read the post properly so I appologize.

[dharkin]

That's my question exactly. I thought there might be a script attached but there isn't any scripts listed in scripts. I tried arrange back /front that did not work for me. Where is "disable field from entry"? Also how does the down arrow appear when the field is clicked?

Thanks for your help and response.

Don

[Genx]

Drop Down Arrow: Right click your field -> Field Control -> Setup ...

Display as: Drop-Down List

Choose your value list

Tick the box that says "Include arrow to show and hide list";

Click Okay

Disabling Entry: Right click your field -> Field Control -> Behaviour -> For the top field, disable "enter in browse mode", for the bottom field, disable "enter in find mode". This way, when the user goes to perform a find, they could for example enter a client name in to the top field - something meaningful vs. an ID which carries little meaning to a user.

[dharkin]

Then send field to backwards, that is it. Thanks so much.

Would you say this is more effective than using lookups?

I have a long list of students in a drop down list I normally use lookups. Also is there an easier way to display 1000 students to select from instead of in a drop down list?

[Genx]

Ah the auto complete option - i forget its somewhere in field setup.

Now to your lookups question - lookups should only ever be used if you need to "capture" the state of data at the point you change the id for example: The price of a product to go on an invoice at the time of purchase - you would use a lookup because products often change and you need be able to generate that invoice at a later stage... if you just dumped related fields on the layout, you would run into issues if a price was to change in your products table... sorry if i'm being a bit vague, lack of sleep.