@PopUpMenu with @xListvalues gives you the list you need and xuserselect command will do the same. However, if your vendor list is very long, I personally like the @xuserselectr which can narrow down the list. Ofcourse it requires a little coding but works great to narrow down your choice.

If you place Bl.. entry in the element, it will give you list of every vendor begins with "Bl  " only.

The topic was discussed in the following link....

http://www.lantica.com/Forum2/cgi-bin/yabb/YaBB.pl?board=gen_disc;action=display...

I will place the whole code, but for better understanding first read the Programming Manual Page 133 and Page 134.  The text you quoted deals only with "start" and "end" part of the xuserselectr command.

The following code goes in Global Code

stat vFieldName as String
stat vStart as String
stat vEnd as String

Subroutine PickList_choose( )

vStart = @left (vFieldName, @in (vFieldName, "..") - 1) + @chr (1)
vEnd = @left (vFieldName,   @in (vFieldName, "..") - 1) + "zzzzzzz"
End Subroutine

Place this in your VendorName Element on element exit event.  I have adjusted it to the name of your element and database name.

if @in(VendorName, "..") > 0 then

     {
           vFieldName = VendorName
           picklist_choose ( )
           
           VendorName = @xUserselectR (@filename, "Vendors!VendorName", "VendorName", vStart, vEnd)

     }



  If the form name is not exactly matching or the element name is not matching, you might have to change it.  Please let me know if this works.  If you need to have Names of all vendors just place ".." in the field.

I believe you are trying to test the code in the preview mode of Sdesigner.  It would not work there as x-family commands and functions would not work in preview. You want to reconcile with database and then test it.

Please let me know if it works or still does not work that way.

Quote:


No I am not using preview. I am using a reconciled version.

The following code goes in Global Code  

stat vFieldName as String
stat vStart as String
stat vEnd as String

Subroutine PickList_choose( )

vStart = @left (vFieldName, @in (vFieldName, "..") - 1) + @chr (1)
vEnd = @left (vFieldName,   @in (vFieldName, "..") - 1) + "zzzzzzz"
End Subroutine

Place this in your PurchaseFrom Element on element exit event of PurchaseFrom element.  I have adjusted it to the name of your element and database name.

if @in(VendorName, "..") > 0 then  

{
 vFieldName = PurchaseFrom
 picklist_choose ( )
 
 PurchaseFrom = @xUserselectR (@filename, "Vendors!VendorName", "VendorName", vStart, vEnd)

}

Bill, after reading your database specification that I did not read earlier, I had to make changes at two places. I think your earlier posting and my post got crossed, so did not get to read your note. I think this should work. If it does not, I will work with you till it does.

Quote:


Bharat,

The more I use them the more uses I find for them. Imagine in your  case the top of your main screen is your generic patient info then you have a subform on the right side that has your patient scheduleing system. Then the rest of your screen has tabs. 1 tab has a tableview subform of all of the previous visits that patient has had. Another tab has a subform to all the billing dates amounts and codes for that patient. You can have subforms that tracks all the meds and scripts you have written. When you select a patient all the data is called from all the separate databases and instantly viewable on 1 form. Using Sesames visibility feature you can make elements appear or disappear based on the user. This will keep you Hippa compliant. If you scan all your E.O.Bs  Imagine your collectors or billing person being able to see each one per activity. I have my test app using checkboxes to go out to a specific directory and placing a check in a box if a document {in your case  say insurance card }is available to view. Think of how much better your compliance can be if you had a checkbox for every paper you needed to have like Ins cards, Hippa release, superbill etc. and if the image was in the system you would know by the checkbox if anything was missing. Either your staff would see it or run a report weekly and work the problem files. I could go on for days but you probably get the jist.

The advantage of the subforms are you can have unlimited amount of events such as co payments a patient owes you 100.00 but he pays 10.00 a month you can just keep adding you never run out of fields. And using Sbasic yo have an element that calculates all billing owed minus each payment and you instantly know how much is owed on a patient by patient basis. But if you need to have an aging you can run it on the separate database and get a true aging based in line items. (I can go on for ever)

Give em a good try but be careful like Sesame Subforms are addicting!

Your conversation sounds fascinating. It is encouraging that others can accomplish lofty goals in sesame. I on the other hand can not get past basic selection lists. 

I took a fresh approach  last night and tried to simplify this process. I am trying this task with 2 single form databases for simplicity.

I started new db, 1 form 2 fields the fields are e1 and e2
I will use the sample zipcodes.db from sesame.

I put

XUserselectr("C:\Sesame\Data\zipcode.db", "zipcode!state", "State", "A"," Z", e2)

In on field exit  program of e1

I thought that when I exited field e1 I would receive a selection list made up of  info from the state field in Zipcode.db  then that info would return the selected state to field e2 once selection was made.

When I leave e1 sesame says working but it just runs indefinitely until I ctrl alt del to menu that says not responding.

What can I possibly have wrong in such a simple task?

Bill,

I have emulated exactly what you have described. I used zipcodes.db. and your logic of XUserselectr("C:\Sesame\Data\zipcode.db", "zipcode!state", "State", "A"," Z", e2)

I think I see why you think it is not working. 

After you exit e1 wait. DO NOT use task mgr to exit. It takes a while for some reason but after a few minutes it will bring up a selection list.

It took about 90 seconds for the selection list to be presented.

Let us know if this thought is correct. Thanks

I realize that it is working on 43042 records in Zipcode database but it still seems like an excessively long time to generate.

Can anyone explain why it is taking so long for this selection box?

I even changed  billgordons logic from a-z to XUserselectr("C:\Sesame\Data\zipcode.db", "zipcode!state", "State", "M"," P", e2) to see if it had a different effect. Still very slow.

Yes Bob you were correct!  Thank you.

Now  Bharat_Naik to follow  your example and have it use what I place in a field and have a selection box . I put this  code  in Global Code   (even though I do not understand what it is doing)
 
stat vFieldName as String 
stat vStart as String 
stat vEnd as String 
 
Subroutine PickList_choose( ) 
 
vStart = @left (vFieldName, @in (vFieldName, "..") - 1) + @chr (1) 
vEnd = @left (vFieldName,   @in (vFieldName, "..") - 1) + "zzzzzzz" 
End Subroutine 

Then I placed this in my  e1 Element on element exit event.  I have adjusted it to the name of my new test  database name. 
 
if @in(e1, "..") > 0 then   
 
{ 
  vFieldName = e1 
  picklist_choose ( ) 
   
  e2 = @XUserselectR ("C:\Sesame\Data\zipcode.db", "zipcode!state", "state", vStart, vEnd) 
 
}

Nothing at all happens. What is wrong? 

Bill, we are using this code for different purpose. What you want to do here is, put State Name in two letters and it should display the list of certain zipcodes for that state only.

The modified code might work for this purpose. I did not try it but this is mainly to shorten the list to display according to the initial string of the value.

As for example

If you want to have list of anything that begin with "Wh..", it will display white, whitehall, white House etc... from the whole list of say 3000 values.

For the example I have merged the example applications Gems.db and Customers.db.

By putting the following code in the On Exit of the Gem_Type LE of the "Gems Types" form of the "Gems Types" database:

// declare some variables - all strings
var v_result as string
var v_start as string
var v_end as string

// set start value to the contents of the field we are in
v_start = Gem_Type

// set the end of the range to that value with a bunch of "z"s
// tacked on to force the full alphabetic range. If the user puts
// "PAR" in the field, this wil force the range to include anything
// that starts with "PAR" through "PARzzzzzzzz" - including
// "PARIS" and "PARKMAN".

v_end = v_start + "zzzzzzzz"
v_start = v_start + @chr(1)

// In this application file, look at the form named "Main Form" for
// the LE named "City" - if its contents are in the range starting
// with what the user typed into "Gem_Type" and ending with
// that value with a bunch of "z"s concatenated on it - then
// return the value in "City" to the User Select list. If the user
// selects one of those City values, return the value in City and
// put it in the variable "v_result".

v_result = @XUserSelectR(@fn, "Main Form!City", "City", v_start, v_end)

// Put the value in "v_result" back into the LE "Gem_Type"
Gem_Type = aa


I got what I think you are asking for using Sesame 1.0.1. Remember that you need to test any of the X functions (XUserSelect, XLookup, etc..) using the actual Sesame runtime - not the Preview option of the Designer.

I stripped out all the error checking and other niceties, so this would be easier to follow. The lines beginning with "//" are comments and you do not need to type those in, they are there to give you a blow by blow explanation of what is happening.

The hard parts here are that you have to remember to use the form name when specifying the "ext select", but *not* use it again for the "source". So the external select is:

Form Name!LE Name - in the example: "Main Form!City"

But the "source" is just "City".

In the your example you would probably use something like:

//------------------ On Exit from ordername
var v_result as string
var v_start as string
var v_end as string

v_start = ordername

v_end = v_start + "zzzzzzzz"
v_start = v_start + @chr(1)
v_result = @XUserSelectR(@fn, "entry!lastname", "lastname", v_start, v_end)
ordername = v_result
//-----------------------------

if your form is named the same thing as your database (it usually is).

I hope this helps. If you have any questions at all - do not be afraid to ask.

What does @error say about it. The X functions will set @error if they fail.

Is it meant to return the same LE that appears in the menu or a different LE on the same form?

Mark, it still does not work with space without putting @chr (1) in var v_start for the search for the whole word which is followed by a space.

"Blue" would not pull up Blue Cross

Bl  will list everything starting with Bl.

Quote:


Yes I am happy. The example is just my speed. I have the selection working now but I am having the same problem Bob described of not having the data from the selection box go to my field.

This is what I have. I pretty much just copied yours and Bharats examples. Thanks


var v_result as string
var v_start as string
var v_end as string

v_start = eventphysican


v_end = v_start + "zzzzzzzz"
v_start = v_start + @chr(1)

v_result = @XUserSelectR(@fn, "physicians!last", "first", v_start, v_end)

eventphysican = v_result 

Thanks once again! 

It works like a charm.

Bob, I understand exactly why it is so important. As a matter of fact, I asked the same question in the following link.

http://www.lantica.com/Forum2/cgi-bin/yabb/YaBB.pl?board=gen_disc;action=display...

Quote: