Negative numbers can be cool for a lot of uses. If I have an indexed true/false field, I don’t want to use just true/false or yes/no or 0/1 because that would create a very inefficient index. Instead, a positive number = true and a negative number = false. The autonumber row id is perfect for true. (0 – id) = flase.
From: [email protected] [mailto:[email protected]] On Behalf Of Karen Tellef Sent: Thursday, September 04, 2014 1:06 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Suggestions - "enter using" form Excellent thought, a negative number is indeed better Karen -----Original Message----- From: Albert Berry <[email protected]<mailto:[email protected]>> To: RBASE-L Mailing List <[email protected]<mailto:[email protected]>> Sent: Thu, Sep 4, 2014 12:55 pm Subject: [RBASE-L] - Re: Suggestions - "enter using" form Karen et al - I tend to use -1 rather than 9999 for this sort of item. I don't have to worry about the company getting 9,999 suppliers and drop downs can have a very simple WHERE SupplierID >= 0. Just a thought. Albert On 9/4/2014 11:29 AM, Karen Tellef wrote: Interesting idea... I'm with you -- if it was my decision I would prompt for necessary info first, then insert into the table and do an "edit using", but unfortunately it's not my choice. So anyway, I put a default value of "9999" in that DBEDit field (which has a popup menu for the selection), so my form expressions evaluate as blank which is good. The "9999" shows in the field until they change it, I'm not sure whether they will care. But I will show it to them as an option! Karen -----Original Message----- From: Javier Valencia <[email protected]><mailto:[email protected]> To: RBASE-L Mailing List <[email protected]><mailto:[email protected]> Sent: Thu, Sep 4, 2014 11:17 am Subject: [RBASE-L] - RE: Suggestions - "enter using" form Karen, This is one of the reason I hardly ever use forms in the ENTER mode. I normally prompt the user for the basic information and then create a new record with basic information that they can edit. In your particular case, can you make the default something other than NULL, say 9999 that has an associated name and address defined as “Undefined – Please update supplier ID” or something along these lines, and when they change the ID it updates to the correct information? I believe there is a place in the form where you can change the default value when used in the ENTER mode; I used to do this all the time in the older versions but since I no longer use this approach I am not sure it is available, but I would think/hope it is still available. Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]?>] On Behalf Of Karen Tellef Sent: Thursday, September 04, 2014 9:23 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Suggestions - "enter using" form I want to use the same form for both editing and entering. The database has ZERO ON and I'd like to keep it that way because there's lots of calcs on the form that need to operate with null values. There is a "supplier" field (column ID), and the customer and address info are displayed on the form using form expressions. The problem is that there is an actual supplier with an ID of 0 !!! So when the form comes up ("enter using master") it displays info for ID = 0 on the form until they go in it and change the supplier. I can null out those values in a "form on after start eep" but as soon as they cursor thru preceding fields it immediately fills back in. OTOH I have to make sure they can actually display info if they choose ID 0, so I cannot change my form expressions to ignore ID 0. I'm thinking I'd have to remove those form expressions and instead use EEPs? On after start capturing whether it's "edit using" and then populating the fields, and then an EEP on exiting the supplier field to display again? Anyone think of anything else I can do? Thanks! Karen
