Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

VFE Date Fields

Trading Post

Last Post by Anonymous 1 second ago

2 Posts

2 Users

0 Reactions

90 Views

RSS

emaher

(@emaher)

Posts: 71

Estimable Member

Topic starter

Maybe this is old news to everyone, but I discovered something odd about date fields in VFE.

When the user enters data into the field, no validation takes place to ensure that what was entered is actually a date. Date fields seem to accept any collection of numbers, slashes and hyphens up to 10 characters long. I could type 1/56/2013 or 37////220, and the system is just fine with it.

How ridiculous is that? I discovered this problem when an invalid date caused one of my crystal reports to crash.

Anyone else encountered this?

Posted : August 20, 2013 11:58 pm

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

Whenever I need to ensure a real date in VFE I use this, its not perfect (will allow February 30) but its close enough to find almost all user mistakes. You could use it to warn users or clear fields with invalid dates or both. It would be nice if GE just fixed it though.

{fn fnValidDate(field){

if (size(field) == 10) then
  if (sub(field,3,1)=="/") then
   if (sub(field,6,1)=="/") then
    if match("01",sub(field,1,1))>0 and match("0123456789",sub(field,2,1))>0 then
     if match("0123",sub(field,4,1))>0 and match("0123456789",sub(field,5,1))>0 then
      if match("12",sub(field,7,1))>0 and match("901",sub(field,8,1))>0 and match("0123456789",sub(field,9,1))>0 and match("0123456789",sub(field,10,1))>0 then
       return "T"
      endif
     endif
    endif
   endif
  endif
endif

return "F"
}}

Posted : August 21, 2013 12:52 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
0 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0