| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 4000.1 | Selection field has /lang=NBS_DATE, too? | ROMEOS::LESLIE_DA | Greetings & Solutions | Mon Mar 21 1994 03:30 | 8 | 
|  |     Is the field that is being used for the selection also have the
    /LANG=NBS_DATE on it?  If so, then you may need to convert the date to
    NBS as part of the recognition processing.  I thought I'd try the
    obvious solution first (and leave the hard parts for those still
    building ALL-IN-1 applications ;*).
    
    HTH,
Dan
 | 
| 4000.2 | Just KEY field ... | TAV02::CHAIM | Semper ubi Sub ubi ..... | Mon Mar 21 1994 06:13 | 18 | 
|  | Dan,
>                 -< Selection field has /lang=NBS_DATE, too? >-
>
>    Is the field that is being used for the selection also have the
>    /LANG=NBS_DATE on it?  If so, then you may need to convert the date to
>    NBS as part of the recognition processing.  I thought I'd try the
>    obvious solution first (and leave the hard parts for those still
>    building ALL-IN-1 applications ;*).
>    
The entry form has two fields; DATE and DESC. DATE is the KEY field and has
/LANG=NBS_DATE.
Thanks,
Cb.
 | 
| 4000.3 | Would appreciate an FLG for a form ... | TAV02::CHAIM | Semper ubi Sub ubi ..... | Mon Mar 21 1994 09:51 | 17 | 
|  | I've been reading the notes which talk about using /LANGUAGE on a key field,
and although it is very clear that it cannot be used, it is NOT 100% clear to
me how to work around this elegantly.
I would appreciate it if some could post the .FLG to an entry form which would
allow me:
1. Enter the date normally (01-APR-1994) - for ADD and CHANGE etc.
2. Store the date as NBS (19940401000000)
3. Display the date as normal (01-APR-1994)
I don't mind storing "dummy" fields if needed, but I wouldn't want to display
anything other than the normal date.
Thanks,
Cb.
 | 
| 4000.4 | If you can't do it with an ENTRY form, then don't use an ENTRY form! | IOSG::MARSHALL | A glitch in reality | Mon Mar 21 1994 10:13 | 8 | 
|  | Personally, I don't like presenting ENTRY forms directly to users at the UI.
I think ENTRY forms should be used for mapping the data file, but that an ARG
form should be used at the UI.  That way, you can put /LANGUAGE on your ARG
form fields, and get all the conversions you require.
Just my humble opinion...
Scott
 | 
| 4000.5 | O.K. ENTRY andf ARG form requested ... | TAV02::CHAIM | Semper ubi Sub ubi ..... | Mon Mar 21 1994 10:31 | 17 | 
|  | Scott,
>
>Personally, I don't like presenting ENTRY forms directly to users at the UI.
>I think ENTRY forms should be used for mapping the data file, but that an ARG
>form should be used at the UI.  That way, you can put /LANGUAGE on your ARG
>form fields, and get all the conversions you require.
>
>Just my humble opinion...
>
No problem agreeing with that. If so, then could you send me an ENT form and
ARG form to do what I requested.
Thanks,
Cb.
 | 
| 4000.6 | Engineers don't work hard enough... | IOSG::MARSHALL | A glitch in reality | Mon Mar 21 1994 20:50 | 6 | 
|  | Sorry, as I'm currently working 12 hour days (no overtime payment) to meet the
Emerald schedule, I don't really have time to provide unofficial, unchargeable
consultancy services too.  Any other time I'd be glad to help; I hope you can
find someone else to help you code the forms.
Scott
 | 
| 4000.7 | Any Volunteers ??? | TAV02::CHAIM | Semper ubi Sub ubi ..... | Tue Mar 22 1994 06:25 | 5 | 
|  | Any volunteers?
Thanks,
Cb.
 |