Skip to main content

[archive] Date Entry Slashes

  • November 5, 2009
  • 6 replies
  • 0 views

[Migrated content. Thread originally posted on 04 November 2009]

Hello,

I have a dream... to enter a date in a date-entry in a continuos way. I mean, when the date entry gets focus, the slashes must dissapear. Then i can type "01012009" and when the focus is lost, the component shows 01/01/2009.

I dream it because actually, you have to put the day, hit the cursor (or point, coma, slash) to jump to the month or year. Yeah, maybe is a lazy request, but when our clients put in a day two thousands dates, removing two keyboards hits from each date input is a must (4000 keyboards hits less!! sorry for keyboards merchants!!).

Well, actually this is posible? in a date entry i mean, i can take a normal entry field and make it, but.... you know.

6 replies

[Migrated content. Thread originally posted on 04 November 2009]

Hello,

I have a dream... to enter a date in a date-entry in a continuos way. I mean, when the date entry gets focus, the slashes must dissapear. Then i can type "01012009" and when the focus is lost, the component shows 01/01/2009.

I dream it because actually, you have to put the day, hit the cursor (or point, coma, slash) to jump to the month or year. Yeah, maybe is a lazy request, but when our clients put in a day two thousands dates, removing two keyboards hits from each date input is a must (4000 keyboards hits less!! sorry for keyboards merchants!!).

Well, actually this is posible? in a date entry i mean, i can take a normal entry field and make it, but.... you know.


Well, actually this is posible? in a date entry i mean, i can take a normal entry field and make it, but.... you know.


i am stupid...
you don't want the entry field solution because there is no date-validation?
you don't want the entry field solution because your users want the calender-view from the date-entry?

in our firm all users are "keyboard merchants" and in all date-entry where the calender-view isn't needed we use entry-fields.

To check the Date i wrote a little programm which i call to validate the date or to get day of week, calweek,...

i attach it...


Short Translation from my doku...


call

call "fKalender" using datum returning exit-status.

field "datum" must be YYYYMMDD

exit-status is in copymember "kalender.def" which give this values:

leap year
03 sjs -> leap year ( 0 = no; 1 = yes)

can be checked with "evaluate true"
88 sj-nein -> is leap year
88 sj-ja -> no leap year

day of week
03 wtg -> day of week (0=sunday; 1=monday;....)

Calender Week
03 kw

Day of Year
03 tdj

Error handling
03 error-z - > Error-KZ
( 00 = all OK; 01 = error day entry; 02 = error month entry )

can be checked with "evaluate true"
88 e-ok - > all OK
88 e-wrongTT - > error day entry
88 e-wrongMM - > error month entry


sorry for my english :)

alot of used variables are from german value...

[Migrated content. Thread originally posted on 04 November 2009]

Hello,

I have a dream... to enter a date in a date-entry in a continuos way. I mean, when the date entry gets focus, the slashes must dissapear. Then i can type "01012009" and when the focus is lost, the component shows 01/01/2009.

I dream it because actually, you have to put the day, hit the cursor (or point, coma, slash) to jump to the month or year. Yeah, maybe is a lazy request, but when our clients put in a day two thousands dates, removing two keyboards hits from each date input is a must (4000 keyboards hits less!! sorry for keyboards merchants!!).

Well, actually this is posible? in a date entry i mean, i can take a normal entry field and make it, but.... you know.
Thanks frosti for share it, we'll think about it, but really is like you said. We want in a same component a date validation and a calendar input too. The only problem is the slashes input.

Before date entrys in the new versions, we have a date validation too and an entry field input, with a button to call a calendar program to fill the entry field if needed, but if we can have it all in the same component... again... you know, things will be clearly.

Anyways, thanks for your post.

[Migrated content. Thread originally posted on 04 November 2009]

Hello,

I have a dream... to enter a date in a date-entry in a continuos way. I mean, when the date entry gets focus, the slashes must dissapear. Then i can type "01012009" and when the focus is lost, the component shows 01/01/2009.

I dream it because actually, you have to put the day, hit the cursor (or point, coma, slash) to jump to the month or year. Yeah, maybe is a lazy request, but when our clients put in a day two thousands dates, removing two keyboards hits from each date input is a must (4000 keyboards hits less!! sorry for keyboards merchants!!).

Well, actually this is posible? in a date entry i mean, i can take a normal entry field and make it, but.... you know.
Thanks frosti for share it, we'll think about it, but really is like you said. We want in a same component a date validation and a calendar input too. The only problem is the slashes input.

Before date entrys in the new versions, we have a date validation too and an entry field input, with a button to call a calendar program to fill the entry field if needed, but if we can have it all in the same component... again... you know, things will be clearly.

Anyways, thanks for your post.

[Migrated content. Thread originally posted on 04 November 2009]

Hello,

I have a dream... to enter a date in a date-entry in a continuos way. I mean, when the date entry gets focus, the slashes must dissapear. Then i can type "01012009" and when the focus is lost, the component shows 01/01/2009.

I dream it because actually, you have to put the day, hit the cursor (or point, coma, slash) to jump to the month or year. Yeah, maybe is a lazy request, but when our clients put in a day two thousands dates, removing two keyboards hits from each date input is a must (4000 keyboards hits less!! sorry for keyboards merchants!!).

Well, actually this is posible? in a date entry i mean, i can take a normal entry field and make it, but.... you know.
We use an entry routine we wrote, which is just a numeric accept (without slashes). And we have a button/function key that calls a calendar. So, we're doing what you were doing. We made it all one component for the most part by creating a common routine to handle it all for us.

[Migrated content. Thread originally posted on 04 November 2009]

Hello,

I have a dream... to enter a date in a date-entry in a continuos way. I mean, when the date entry gets focus, the slashes must dissapear. Then i can type "01012009" and when the focus is lost, the component shows 01/01/2009.

I dream it because actually, you have to put the day, hit the cursor (or point, coma, slash) to jump to the month or year. Yeah, maybe is a lazy request, but when our clients put in a day two thousands dates, removing two keyboards hits from each date input is a must (4000 keyboards hits less!! sorry for keyboards merchants!!).

Well, actually this is posible? in a date entry i mean, i can take a normal entry field and make it, but.... you know.
We use an entry routine we wrote, which is just a numeric accept (without slashes). And we have a button/function key that calls a calendar. So, we're doing what you were doing. We made it all one component for the most part by creating a common routine to handle it all for us.

[Migrated content. Thread originally posted on 04 November 2009]

Hello,

I have a dream... to enter a date in a date-entry in a continuos way. I mean, when the date entry gets focus, the slashes must dissapear. Then i can type "01012009" and when the focus is lost, the component shows 01/01/2009.

I dream it because actually, you have to put the day, hit the cursor (or point, coma, slash) to jump to the month or year. Yeah, maybe is a lazy request, but when our clients put in a day two thousands dates, removing two keyboards hits from each date input is a must (4000 keyboards hits less!! sorry for keyboards merchants!!).

Well, actually this is posible? in a date entry i mean, i can take a normal entry field and make it, but.... you know.
We use an entry routine we wrote, which is just a numeric accept (without slashes). And we have a button/function key that calls a calendar. So, we're doing what you were doing. We made it all one component for the most part by creating a common routine to handle it all for us.