[RBG7-L] - Re: Scrolling Region behavior

[Javier Valencia]

Dennis: I e-mailed you a form that works with Concomp (table Invoice Header as you suggested) and does what you want; you can use it as a sample. Javier,   Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66062-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 ================================================ Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all system and destroy all copies. ======================================================   -----Original Message----- From: rbg7-l@rbase.com [mailto:[EMAIL PROTECTED]On Behalf Of Dennis Fleming Sent: Wednesday, August 17, 2005 3:55 PM To: RBG7-L Mailing List Subject: [RBG7-L] - Re: Scrolling Region behavior   Thanks Bernie. In a scrolling region, if I have a component Id of Equipment_Description for a variable, and I use getproperty to lookup the right description to place it on the form, my experience is that it will put it in all the rows. And, it is an FK table so the same equipment number can be on multiple rows. I'll try it again. Dennis ***** At 04:28 PM 8/17/2005, you wrote: Dennis, Sorry, I meant to say form variable (have reports on my brain) But if you get the part no by using the getproperty, then it shouldn't duplicate the description into other rows. Assuming of course, that your part no is unique in the form.   Bernie Lis   ----- Original Message ----- From: Dennis Fleming To: RBG7-L Mailing List Sent: Wednesday, August 17, 2005 1:46 PM Subject: [RBG7-L] - Re: Scrolling Region behavior Bernie, This was a form, not a report. The problem I have had in the past with Getproperty is that it propagates the variable into every row with that component id. But thanks anyway. Dennis ***** At 11:13 AM 8/17/2005, you wrote: Instead of a report variable, use an eep based on the entered value of Equip_number. Set a component id in the Equip_Number property. use GETPROPERTY vNo TEXTVALUE 'vPartNo' in your eep where vNo is the component id and vPartNo will contain the text value of  Equip_Number. Then you can do a select to get the description. Then use PROPERTY TABLE <FormTableName> 'REFRESH' Bernie Lis ----- Original Message ----- From: "Dennis Fleming" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <rbg7-l@rbase.com> Sent: Wednesday, August 17, 2005 10:01 AM Subject: [RBG7-L] - Scrolling Region behavior Looking for a workaround to avoid "slot machine" behavior for variable look ups. Scrolling region rows have two popup dbedit values and form flashed through all possible values for a different variable after popup is selected and you move to the next row, making form run very slow. In from Variables: vEquipDesc = Equip_Desc in Equipment where Equip_Number = Equip_Number After selecting the popup value for a different column in the row and moving to the next row, all possible values for vEquipDesc are displayed on the row you just left. Anyone else observe this behavior and/or have a fix/workaround? TIA, Dennis ***** Dennis Fleming IISCO http://www.TheBestCMMS.com Phone: 570 775-7593 Mobile: 570 351-5290   Dennis Fleming IISCO http://www.TheBestCMMS.com Phone: 570 775-7593 Mobile: 570 351-5290 Dennis Fleming IISCO http://www.TheBestCMMS.com Phone: 570 775-7593 Mobile: 570 351-5290