Hey, guys, there will always be room for new ways of doing things. The
Kernel tools are there and heavily used. But as Kevin found, it didn't
quite work the way he needed. Kevin has fulfilled his need with the tool he
has constructed. There are numerous ways of providing services that are
needed. The VistA experience is an opportunity for people to use tools
provided and to build their own solutions. I would encourage Kevin to
document his solution and submit it to WorldVistA to manage the tool and
make it available to others so they can use this tool to make their own
solutions. Cool.
Best wishes; Chris
----- Original Message -----
From: "smcphelan" <[EMAIL PROTECTED]>
To: <hardhats-members@lists.sourceforge.net>
Sent: Tuesday, May 17, 2005 11:37 AM
Subject: Re: [Hardhats-members] Custom Fileman date output formatting.
> XLFDT expects a valid date input. So no it cannot convert a number from
> 1-12 to a month. I am not sure what you mean about not displaying year
> only. Here are some simple examples of what it can do that addresses most
> of your comments:
>
> W $$FMTE^XLFDT(3000000)
> 2000
>
> W $$FMTE^XLFDT($$NOW^XLFDT,"5PZ")
> 05/17/2005 2:19:25 pm
>
> W $$FMTE^XLFDT($$NOW^XLFDT,"P")
> May 17, 2005 2:19:39 pm
>
> W $$FMTE^XLFDT(3050805)
> Aug 05, 2005
>
> W $$DOW^XLFDT(DT)
> Tuesday
>
> W $$DOW^XLFDT(DT,1)
> 2
>
> Does you utility allow for the conversion of the ANSI standard M
date,time,
> $H?
>
> Does your utility allow for the conversion of FM date.time to HL7
date.time
> and vice versa?
>
> Does you utility allow for the conversion of $H to HL7 date.time?
>
> Does your utility allow for the adding (or subtracting) of either days,
> hours, minutes, or seconds to a FM (or $H) date.time and return a valid FM
> (or $H) date.time?
>
> Does you utility allow for the conversion of date.time to a numeric number
> that can be used in mathematical calculations?
>
> Does your utility allow for time zones and as such for UCT?
>
> Does your utility account for all leap years over 1000 year time frame?
>
> If you can answer Yes to all of these questions, then your utility
> approaches the robustness of XLFDT.
>
> I question the usefulness of "at exactly" in a date when dealing with
> physicians. When was the last time any patient had their scheduled
> appointment kept by the practice "at exactly" the scheduled date and time?
>
>
>
>
> ----- Original Message -----
> From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
> To: <hardhats-members@lists.sourceforge.net>
> Sent: Tuesday, May 17, 2005 12:37 PM
> Subject: Re: [Hardhats-members] Custom Fileman date output formatting.
>
>
> > > See XLFDT it is more robust than what you show here.
> >
> > I didn't notice that you say XLFDT is MORE robust than
> > what I showed. Can you give an example that you feel
> > my function would not be able to do?
> >
> > Kevin
> >
> >
> > --- smcphelan <[EMAIL PROTECTED]> wrote:
> >
> > > It is nice you have developed a M API to convert
> > > dates. Everything you show
> > > here (except for the at exactly) has been part of
> > > VistA for 10 years or
> > > more... See XLFDT it is more robust than what you
> > > show here.
> > >
> > > ----- Original Message -----
> > > From: "Kevin Toppenberg" <[EMAIL PROTECTED]>
> > > To: "Hardhats Sourceforge"
> > > <hardhats-members@lists.sourceforge.net>
> > > Sent: Sunday, May 15, 2005 8:37 PM
> > > Subject: [Hardhats-members] Custom Fileman date
> > > output formatting.
> > >
> > >
> > > > I may have just reinvented the wheel, but I don't
> > > > think so. I have just finished a function that
> > > will
> > > > format fileman dates in any arbitrary way, based
> > > on
> > > > format strings. For example:
> > > >
> > > > w $$DTFormat(FMDate,"mm/dd/yy") --> 10/13/79
> > > > w $$DTFormat(FMDate,"mm/dd/yyyy") --> 10/13/1979
> > > > w $$DTFormat(FMDate,"mmm dd,yyyy") --> Oct 13,1979
> > > > w $$DTFormat(FMDate,"mmmm dd,yyyy") --> October
> > > > 13,1979
> > > > w $$DTFormat(FMDate,"mmmm dd,yyyy 'at exactly'
> > > HH:MM
> > > > #") --> October 13,1979 at exactly 2:15 pm
> > > >
> > > > The format string allows any mix and match order.
> > > It
> > > > has appropriate codes for formatting 24 vs 12 hr
> > > > clock. Month numbers, short-names, or long names.
> > > > Year in 2 or 4 digits. Numbers with or with-out a
> > > > leading 0.
> > > >
> > > > This function is based roughly on the way that
> > > Delphi
> > > > handles datetime formatting.
> > > >
> > > > If anyone wants a copy of the function let me
> > > know. I
> > > > just tried to post it on the wikki, and apparently
> > > the
> > > > Sourceforge host is down for the moment.
> > > >
> > > > Kevin
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
> _______________________________________________
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
>
>
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
