Thanks Cameron, Kevin
--- Cameron Schlehuber <[EMAIL PROTECTED]> wrote: > Here's an update on this problem. > > Quoting from the NOIS: > > Only the patient's last name is run through > $$FORMAT^XLFNAME7. So if the > user adds characters that are removed before > storing, nothing is found and > the DPTLK routines either offer to add a new patient > or displays ?? > depending on the option being used. > > A fix will be included in patch DG*5.3*641 scheduled > for release by May 1, > 2005. > > -----Original Message----- > From: Cameron Schlehuber > [mailto:[EMAIL PROTECTED] > Sent: Monday, January 03, 2005 4:52 PM > To: 'hardhats-members@lists.sourceforge.net' > Subject: RE: [Hardhats-members] Unusual search > failure. > > You're right! The way it works on the Patient file > isn't the way it should > be! It works correctly on the New Person file. > I'll submit a NOIS for that > problem. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Kevin > Toppenberg > Sent: Monday, January 03, 2005 3:19 PM > To: hardhats-members@lists.sourceforge.net > Subject: RE: [Hardhats-members] Unusual search > failure. > > But this sets up a situation where the process of > converting from external to internal form causes the > name to get "lost". I.e. I put a name into the > database, then search for that same name and find it > has "disappeared." > > By looking at that transform you mention, I see that > I > can use: set INTNAME=$$FORMAT^DPTNAME(.PATNAME,3,30) > and then search for INTNAME -- but this is far from > user friendly. Why doesn't the search system do > this > external-to-internal conversion automatically before > searching? > > Anyway, thanks for your help. > > Kevin > > > > --- Cameron Schlehuber <[EMAIL PROTECTED]> > wrote: > > > Note as the Description (on the .01 field in the > New > > Person file) states, > > the "value must be 3-35 characters in length and > may > > contain only uppercase > > alpha characters, spaces, apostrophes, hyphens and > > one comma. All other > > characters and parenthetical text will be > removed." > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] > > On Behalf Of Walton, > > Edward NMN(WSH) > > Sent: Monday, January 03, 2005 12:57 PM > > To: 'hardhats-members@lists.sourceforge.net' > > Subject: RE: [Hardhats-members] Unusual search > > failure. > > > > Did you mean ^DPT the ^VA(200 file is the > newperson > > file? > > > > Ed > > > > -----Original Message----- > > From: Kevin Toppenberg [mailto:[EMAIL PROTECTED] > > Sent: Monday, January 03, 2005 10:41 AM > > To: Hardhats Sourceforge > > Subject: [Hardhats-members] Unusual search > failure. > > > > Hey all, > > > > I thought I was getting the hang of fileman, but I > > have found a quirk that I > > don't understand. > > > > I add a patient with UPDATE^DIE. The patient's > name > > is specified to be > > "DOE,JOHN P." This happens with no problem. When > I > > look in ^VA(200, I can > > see the added patient ("DOE,JOHN P" -- with no > ".") > > > > The problem occurs when I search for the patient. > I > > am using FIND^DIC to > > lookup the patient. The problem occurs if I > include > > the "." in the search > > value. i.e. > > "DOE,JOHN P." --> search fails > > "DOE,JOHN P" --> search succeeds. > > > > Is this standard? Is there a flag for FIND^DIC > that > > can prevent this > > pickiness? > > > > Thanks > > Kevin > > > > > > > > > > __________________________________ > > Do you Yahoo!? > > Take Yahoo! Mail with you! Get it on your mobile > > phone. > > http://mobile.yahoo.com/maildemo > > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by: Beat the > > post-holiday blues > > Get a FREE limited edition SourceForge.net t-shirt > > from ThinkGeek. > > It's fun and FREE -- well, > > almost....http://www.thinkgeek.com/sfshirt > > _______________________________________________ > > Hardhats-members mailing list > > Hardhats-members@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/hardhats-members > > > > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by: Beat the > > post-holiday blues > > Get a FREE limited edition SourceForge.net t-shirt > > from ThinkGeek. > > It's fun and FREE -- well, > > almost....http://www.thinkgeek.com/sfshirt > > _______________________________________________ > > Hardhats-members mailing list > > Hardhats-members@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/hardhats-members > > > > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by: Beat the > > post-holiday blues > > Get a FREE limited edition SourceForge.net t-shirt > > from ThinkGeek. > > It's fun and FREE -- well, > > almost....http://www.thinkgeek.com/sfshirt > > _______________________________________________ > > Hardhats-members mailing list > > Hardhats-members@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/hardhats-members > > > > > > > __________________________________ > Do you Yahoo!? > Read only the mail you want - Yahoo! Mail SpamGuard. > > http://promotions.yahoo.com/new_mail > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the > post-holiday === message truncated === __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
