Reading through the threads of creating a pop up list or selection box I tried to apply this to my application, with some changes, but they are not working.

I have two applications with one db per (both will eventually be merged and the x commands will need to be changed, but).  The first db is Buildercodes, which holds the information per client per project.  Example : builder will have many projects, and each project is billed individually, so each project has a "buildercode" which is unique.  For further example the builder Toll Bros. will have two projects one called South Riding Glen, one called South Riding Fairways, but the builder codes/client information is differents so the "buildercode" is different, TOLL26.3 and TOLL26.4, respectfully.

In the second database we store the individual permits issued for the above projects, mind that we have over 80 active projects.  When entering a permit for a project, I have xlookup pull the project, section, etc from the first database using the buildercode (TOLLxx.x).

What I want to acomplish, if possible, is to have the user start typing in TOLL in the buildercode element and then a pop up list of the "Projects" is given, and when the correct "Project" is selected if will fill in the "buildercode", then the existing xlookup commands will fill in the rest.

As you can see, doing the selection list from the element that is being filled in can go in length of 50+ and still only showing the buildercode only gives the code and not the project, so mistakes are more easily made at entry, ie picking a word with a number and not the project name.

Any Advice?????

Duane

The "or" is correct.

To explain further, currently the Q&A databases are bldcodes.dtf and permits.dtf.  When a user enters a new permit into permits.dtf the user addes the "code" which relates to a "buildercode" in bldcodes.dtf.  Where we have problems is when a typo is made to that entry and the permit is liked to the wrong project.

It is hard to explain, but here goes about how bldcodes is setup.  First is the standard information that one would keep for a client, name, address, phone, etc.., but the unique "key" we use is called buildercode.  The code is usually the first 3 to 5 letters of the clients name, then a number, and sometimes a subnumber.  This is hard to put into words without some examples.

Client, Project, Code
Toll Bros., South Riding Glen, TOLL26.1
Toll Bros., South Riding Fairway, TOLL26.2
Toll Bros., Belmont Carriages, TOLL23.4
Toll Bros., Belmont Tournaments, TOLL23.8

Now this just represents one of many clients that have projects which are actually in the same subdivision, but they are billed to different managers.  So, the data entry errors have been either the user dosen't remember the correct code or needs to close permits.dtf, search bldcodes.dtf, then reopen and enter a permit.

To help avoid these memory errors and constant searching then adding, I would like to do a selection list, but with a small catch.

I have created and have no problem doing just for the element code (showing a list of all the codes 1600+).  I would like to make a pick list that narrows down the codes and help reduce errors, by having the it use the first couple of letters typed, but instead of showing the codes, to show the project.  Once the project is selected it will populate the code element with the correct code.

If this makes no sense, I appologize, but our clients are not your standard clients on how they are billed since each project is somewhat of a client of its own, therefore each project gets its own code, but to keep them somewhat related they have the numbered parts.

Is what I'm looking for possible?

Bharat,

I was going down the same thought process you are.

With the features we understand from Sesame so far, I would do it as you explained.

Quote:


Duane,

Place it all in the on element exit.

I find that the simplest ways to accomplish these tasks are 1 step at a time.

First in the database you are going to retrieve the data from create the new element as Bharat has suggested.  The first part of your element needs to be what you will actually search on. In Bharats example
You are making an element just for displaying, this is how your user will decide what company to choose
So in the lines below you started with the code first then company name then project name
This gave you data formatted like such

TOLL26.1, Toll Bros., South Riding Glen,
TOLL26.2, Toll Bros., South Riding Fairway,
TOLL23.4, Toll Bros., Belmont Carriages,
TOLL23.8, Toll Bros., Belmont Tournaments,

So when you type TOL in your search element, it would return all the choices above in the selection box.

(The simplest method for you at this time might be to mass update existing data into the new display element and add logic so every time new data is entered it places the data correctly in the display element.)

Once you have your display data element correct in the database you are retrieving from step 2 will be to open the database that holds the element you are going to have the selection box used with  and  add the code Bharat described earlier into the on element exit program area.

I would then reconcile and test the database and be certain the selection box is working properly.

Once you are happy with the selection box move to step 3 and use Xlookup logic to fill the fields.

If anything is not clear give us a shout. We are all learning together, and between all of us together we will figure it out. 

All fixed it was the line v_Result, I had left the source as "code", it should have been "buildercode".

After testing it worked perfectly, uncommented my xlookup statements and now the whole thing works perfect.

THANK YOU ALL FOR THE GREAT ADVICE, ONCE AGAIN