@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!