Re: [RBASE-L] - DBGrids

2016-10-13 Thread A. Razzak Memon 

At 12:52 PM 10/13/2016, karentellef via RBASE-L wrote:


I was looking at your "form control & properties" document on your website.
It doesn't (yet) show TEXTVALUE as being available for DBGrids.

I guess I'll have to play around with this (is it in Enterprise 
only? One of my 10
clients is not on enterprise as we transition off DOS).  The command 
doesn't seem
to make sense to me, however.  You assign a ComponentID to the Grid 
itself, not to
a particular field.  So it looks like you have to be IN the 
secondary field and

then assign the value on entry into that field?

If so, that's not what I was looking for.  Let's say you're in the 
first column, a
CustomerID. You choose a CustomerID, and you want another field 
farther down the row
be assigned a particular lookup discount%  (editable, so no form 
variable).  When you
exit the CustomerID field, how can you make that other field have 
the discount% in it

right away, without having the user actually go into that field?

Again, sorry if I'm not understanding your examples.



Nothing will make sense until you use the right version/build and 
understand the purpose
behind the PROPERTY  TEXTVALUE 'value' command 
when used for

Enhanced DB Grid control.

This command and technique, as clearly illustrated in three images, 
will change the value
of "any selected cell" of the Enhanced DB Grid. So, the emphasis is 
on the "selected cell".


In Enhanced DB Grid, you don't assign the ComponentID to a particular 
field; instead you
assign to Enhanced DBGrid itself. Then, use all cool options to 
accomplish your goal.


For more details, supported commands, and examples, refer to R:Docs X 
(Version 10).


Very Best R:egards,

Razzak.




--
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [RBASE-L] - DBGrids

2016-10-13 Thread A. Razzak Memon 

At 12:52 PM 10/13/2016, karentellef via RBASE-L wrote:


I was looking at your "form control & properties" document on your website.
It doesn't (yet) show TEXTVALUE as being available for DBGrids.

I guess I'll have to play around with this (is it in Enterprise 
only? One of my 10
clients is not on enterprise as we transition off DOS).  The command 
doesn't seem
to make sense to me, however.  You assign a ComponentID to the Grid 
itself, not to
a particular field.  So it looks like you have to be IN the 
secondary field and

then assign the value on entry into that field?

If so, that's not what I was looking for.  Let's say you're in the 
first column, a
CustomerID. You choose a CustomerID, and you want another field 
farther down the row
be assigned a particular lookup discount%  (editable, so no form 
variable).  When you
exit the CustomerID field, how can you make that other field have 
the discount% in it

right away, without having the user actually go into that field?

Again, sorry if I'm not understanding your examples.



Nothing will make sense until you use the right version/build and 
understand the purpose
behind the PROPERTY  TEXTVALUE 'value' command 
when used for

Enhanced DB Grid control.

This command and technique, as clearly illustrated in three images, 
will change the value
of "any selected cell" of the Enhanced DB Grid. So, the emphasis is 
on the "selected cell".


In Enhanced DB Grid, you don't assign the ComponentID to a particular 
field; instead you
assign to Enhanced DBGrid itself. Then, use all cool options to 
accomplish your goal.


For more details, supported commands, and examples, refer to R:Docs X 
(Version 10).


Very Best R:egards,

Razzak.




--
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [RBASE-L] - DBGrids

2016-10-13 Thread karentellef via RBASE-L 
I was looking at your "form control & properties" document on your website.  
It doesn't (yet) show TEXTVALUE as being available for DBGrids. 

I guess I'll have to play around with this (is it in Enterprise only? One of my 
10
clients is not on enterprise as we transition off DOS).  The command doesn't 
seem 
to make sense to me, however.  You assign a ComponentID to the Grid itself, not 
to a
particular field.  So it looks like you have to be IN the secondary field and 
then assign 
the value on entry into that field?

If so, that's not what I was looking for.  Let's say you're in the first 
column, a CustomerID.
You choose a CustomerID, and you want another field farther down the row be
assigned a particular lookup discount%  (editable, so no form variable).  When 
you
exit the CustomerID field, how can you make that other field have the discount% 
in it
right away, without having the user actually go into that field?

Again, sorry if I'm not understanding your examples.

Karen

 

 

 

-Original Message-
From: A. Razzak Memon <raz...@rbase.com>
To: rbase-l <rbase-l@googlegroups.com>
Sent: Thu, Oct 13, 2016 11:41 am
Subject: Re: [RBASE-L] - DBGrids

At 11:45 AM 10/12/2016, karentellef via RBASE-L wrote:

>I don't have RDocs, but I did look at the Form Controls & Properties PDF
>file that you have online, and looked thru the pages and pages of properties
>available for "Enhanced DBGrid".  Unless I've missed something, I don't see
>anything that appears to work like the TEXTVALUE property.

Are you sure?

What version and build of R:BASE X Enterprise are you using?


>I see the properties to retrieve the current values of a cell, but nothing
>to assign a value to another cell.


Here's how:

01. Start R:BASE X Enterprise (Version 10, Build: 10.0.2.11013 or higher)
 Image: RBGXE.jpg

02. CONNECT dbname and then open the form with Enhanced DB Grid Control in
 Form Designer

03. Assign the Component ID to Enhanced DB Grid

04. Run the form using the Run Form (Live) Button or [Shift+Ctrl+F9]

05. Select the DBGrid Cell and use the "PROPERTY  TEXTVALUE value"

 See attached images ...
 EnHanced_DB_Grid_TEXTVALUE_01.JPG
 EnHanced_DB_Grid_TEXTVALUE_02.JPG
 EnHanced_DB_Grid_TEXTVALUE_03.JPG

That's all there is to it.

Enjoy the presentation!

Very Best R:egards,

Razzak


-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [RBASE-L] - DBGrids

2016-10-12 Thread karentellef via RBASE-L 
I don't have RDocs, but I did look at the Form Controls & Properties PDF file
that you have online, and looked thru the pages and pages of properties 
available
for "Enhanced DBGrid".  Unless I've missed something, I don't see anything that
appears to work like the TEXTVALUE property.

 
I see the properties to retrieve the current values of a cell, but nothing to 
assign
a value to another cell.

Sorry, I must be blind!  (Actually, I sorta am, I do have an eye infection)


 Karen


 

-Original Message-
From: A. Razzak Memon <raz...@rbase.com>
To: rbase-l <rbase-l@googlegroups.com>
Sent: Wed, Oct 12, 2016 10:37 am
Subject: Re: [RBASE-L] - DBGrids

At 10:11 AM 10/12/2016, karentellef via RBASE-L wrote:

>I'm going to try like heck to replace all my old 7.6-era scrolling 
>regions with DBGrids,
>so I need to find out the best way to do those easy scrolling region 
>things within a
>DBGrid.  The one I'm having trouble with would be doing the 
>equivalent of "PROPERTY
>componentID TEXTVALUE <whatever".  Within a DBGrid, how can I assign 
>a value to another
>column based on something in the current column?  Or do I have to go 
>behind the scenes
>and update a table and refresh?

Got R:Docs X (Version 10)?

http://www.rbaseupdates.com
http://www.rupdates.com

Take a close look at the complete list of PROPERTY/GETPROPERTY 
commands, and then use the
one you see fit.

Very Best R:egards,

Razzak


-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [RBASE-L] - DBGrids vs. Scrolling Regions

2016-06-05 Thread karentellef via RBASE-L 
Oh, I see...  Are you saying that you calculate the lookups and actually update 
the update values to columns that are in the table?  Would just have to have 
enough dummy columns to use so that multiple users could be running different 
forms each doing different kinds of lookups.  Not a bad idea!

Or are you putting a value in an extra column and associating that with a 
lookup, say to a view?

What I was thinking in my case is that the table always has the column CustPart 
in it, but of course that column is located on the form by itself with no 
lookup.  If I had a view or temp table with the calculated Avg Production per 
CustPart, then I could have a computed column in my form table called something 
like CustPart2=Custpart, locate CustPart2 on the form, and have the lookup be 
to the view where custpart = custpart2

Karen

 

 

 

-Original Message-
From: Dan Goldberg <d...@lancecamper.com>
To: rbase-l <rbase-l@googlegroups.com>
Sent: Sun, Jun 5, 2016 11:51 am
Subject: RE: [RBASE-L] - DBGrids vs. Scrolling Regions



You can do lookups in enhanced db grids. I just use extra columns that I do not 
use for the lookup column. I have a couple of them running in production.
 
If you need an example, let me know.
 
Dan Goldberg
 
From: karentellef via RBASE-L [mailto:rbase-l@googlegroups.com]
Sent: Sunday, June 5, 2016 9:14 AM
To: rbase-l@googlegroups.com
Subject: [RBASE-L] - DBGrids vs. Scrolling Regions
 
Sitting here watching the French Open on a Sunday.. and thinking about 
something that I've always struggled with in RBase.

Scrolling regions have been there for decades, used to be the ONLY way for us 
to display multi-row data!  When DBGrids were introduced in 7.x, IMO they've 
always looked more professional, more windows-like.  I wish I could replace 
every region I have with a DBGrid.

But my only issue is when I am displaying lookups to other tables, data that 
has nothing to do with a column in the master table (unlike, say, displaying 
the name of a customer rather than the table's ID which is totally doable 
within a grid).  Look at the print-screen below.  The squared items are form 
variables located on each row, lookups to display daily production values and 
the last machine the item was produced on.   These are lookups to other tables 
and have nothing to do with data in the master table other than using its 
part#.  And the user wants to see the data on every row that displays, does not 
want to click on a row and have the data displayed off to the side (which of 
course would be easy to do with a grid), and also wants the data to be directly 
editable.

Has anyone put this kind of data into multiple views, and then had "dummy" 
columns in the master table that you can link to the view using a "pre-defined 
expression" for the column?  Anyone do that?  Or another nifty trick I can use?

Karen




 

 
-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
torbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: [RBASE-L] - DBGrids vs. Scrolling Regions

2016-06-05 Thread Dan Goldberg 
You can do lookups in enhanced db grids. I just use extra columns that I do not 
use for the lookup column. I have a couple of them running in production.

If you need an example, let me know.

Dan Goldberg

From: karentellef via RBASE-L [mailto:rbase-l@googlegroups.com]
Sent: Sunday, June 5, 2016 9:14 AM
To: rbase-l@googlegroups.com
Subject: [RBASE-L] - DBGrids vs. Scrolling Regions

Sitting here watching the French Open on a Sunday.. and thinking about 
something that I've always struggled with in RBase.

Scrolling regions have been there for decades, used to be the ONLY way for us 
to display multi-row data!  When DBGrids were introduced in 7.x, IMO they've 
always looked more professional, more windows-like.  I wish I could replace 
every region I have with a DBGrid.

But my only issue is when I am displaying lookups to other tables, data that 
has nothing to do with a column in the master table (unlike, say, displaying 
the name of a customer rather than the table's ID which is totally doable 
within a grid).  Look at the print-screen below.  The squared items are form 
variables located on each row, lookups to display daily production values and 
the last machine the item was produced on.   These are lookups to other tables 
and have nothing to do with data in the master table other than using its 
part#.  And the user wants to see the data on every row that displays, does not 
want to click on a row and have the data displayed off to the side (which of 
course would be easy to do with a grid), and also wants the data to be directly 
editable.

Has anyone put this kind of data into multiple views, and then had "dummy" 
columns in the master table that you can link to the view using a "pre-defined 
expression" for the column?  Anyone do that?  Or another nifty trick I can use?

Karen

[rbase.png]


--
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.