[RBASE-L] - Not a Bug In Rbase 7.6 DB Grid object, default column width of 64

[Michael J. Sinclair]

Hi Jan,
Your method worked perfectly! Thanks!
Mike

-------------- Original message from "jan johansen" <j...@jjcalibrations.com>: --------------

Michael,
 

I noticed your P.S. has not been answered.

 

In my opinion the easiest method to accomplish your task is that use 2 FORM lookup variables.

For example;

1. Define a Variable on your unique row i.e.

Name: vLUCustID

Type: INTEGER

_expression_: (CustomerID)

Table Name: Customers

2. Lookup the column as such

Name: vLUCustName

Type: TEXT

_expression_: CompanyName IN Customers WHERE CustomerID = .vLUCustID

Table Name: Customers

 

There are unquesionaly other ways to do this but I think this is the easiest to explain.

 

Jan

 

 

 

 

-----Original Message-----
From: "Michael J. Sinclair" <mj...@bellsouth.net>
To: rbase-l@rbase.com (RBASE-L Mailing List)
Date: Sat, 17 Oct 2009 22:43:16 +0000
Subject: [RBASE-L] - Bug In Rbase 7.6 DB Grid object, default column width of 64 ignored.

Hi All,

I have been trying to incorporate the OnKeyPress into my form. The column sizes were too big, bigger than the columns in the OnKeyPress example, even though the column width in the OnKeyPress were set to be 150, and my column widths were all left alone at the default of 64. Well....as soon as I changed the column size to ANYTHING but 64, the column sizes seemed to work just fine. Leaving them set at the default width of 64 made the columns larger....which made the group of columns much too wide...wider than the size of the object which was forcing me to use a horizontal scroll bar.

Can anybody confirm that before I report it?

Mike

PS: Once I have selected the row I want, how do I get the column value of the selected row into a variable so I can use the data elsewhere in my form?