Conceptually, cross-references are pretty simple. When a field is
edited, first the kill logic, then the set logic is executed for that
cross-reference. This makes it easy to identify the record or records
for which a field has a given value. At least that's the usual case.
Some of the more
The percent routines are the _* routines when you are working on a GTM system
and as I recall, that is how they exported out of Cache as well. Hunt for
them using a wild card in front of them in Studio to see what you find like
*ZOSV* or something like that. I also think that you cannot see
That's right, but if there is no data to cross-reference, no index will
be built. Could that be the problem?
(Note also that ^DIK is also used to delete records, so look before you
leap!)
Gregory Woodhouse
[EMAIL PROTECTED]
On Apr 25, 2005, at 10:29 PM, chuck5566 wrote:
I know that you
If anyone is aware of opportunities for a nurse with project management
experiance and an interest in promoting Open Source soultions for
healthcare, please contact me.
Alric
---
SF email is sponsored by - The IT Product Guide
Read honest
Bhaskar,
I think Mano was referring to the handling of strings with UTF-8 encoding. That
is what
his linux desktop was configured for at the beginning of the discussion. When
he would
type into a terminal with GTM (or without, I presume), the greek characters
would be
entered as two bytes. Not
There is one issue I have with the WorldVistA VistA codebase. I mentioned
this at Boston. But it needs to be brought up in this larger context.
1. Who has access to this code base to make any supposed modifications to
it?
2. What relationship will all these scripts have to the official codebase?
I have applied for the domains OpenSourceVistA .com and .org and already have
OpenSourceVistA.net . Should WorldVistA desire to use these, I will transfer
them. The TM fees are a bit steep though, so I will wait to see if WV wants
them before applying for that!
On Monday 25 April 2005 06:52
As the author of one such script, I would agree that
it is a user beware situation. It would be nice if
the work could be expanded upon and made more safe.
But one has to start somewhere.
Kevin
--- steven mcphelan [EMAIL PROTECTED] wrote:
There is one issue I have with the WorldVistA VistA
user beware is standard fare in software EULA's so the good news it
would not be unique for this caveat to be added to VistA code.
Joseph
Kevin Toppenberg wrote:
As the author of one such script, I would agree that
it is a user beware situation. It would be nice if
the work could be expanded
Working with the Medicine package i ordered a
GI procedure (laprascopy)from CPRS. when I saw the "VA for
the alert i faced the following
problem:
Consult/Request Alerts Apr
26, [EMAIL PROTECTED]:58:38
Page: 1 of 0
TESTING,Y
907-02-0205 FEB 2,2005
(0) Wt (lb):
Requested St No.
Watching the discussion on this list, I'm not at all sure that #2 isn't
the majority opinion!
Gregory Woodhouse
[EMAIL PROTECTED]
On Apr 25, 2005, at 5:19 AM, JohnLeo Zimmer wrote:
Of course, the name is just bath water and must not obscure the core
reality which, IMHO, is not the mere
Greg is right about where the code is stored (in the DD, the xrefs are
in a multiple in the field) and that you should use FM to edit them. In
practice, though, some programmers do edit the code directly in the
global for some types of xrefs (like regular, etc.) where FM won't give
you access
Kevin asked:
So here are my questions:
1. Apparently there is some M code associated with
each cross-reference. When is this code executed?
For every add/edit/delete of that field, FileMan triggers the
appropriate Set or Kill. Also if you re-index the file, the code will
be executed.
2.
Sorry I got behind on my email. Did this problem get fixed?tx/t
-Original Message-
From: [EMAIL PROTECTED] [mailto:hardhats-
[EMAIL PROTECTED] On Behalf Of Nancy Anthracite
Sent: Saturday, April 23, 2005 10:46 AM
To: hardhats-members@lists.sourceforge.net
Subject: Re:
Thanks Greg,
Kevin
--- Greg Kreis [EMAIL PROTECTED] wrote:
Greg is right about where the code is stored (in the
DD, the xrefs are
in a multiple in the field) and that you should use
FM to edit them. In
practice, though, some programmers do edit the code
directly in the
global for some
Anna,
I think Bhaskar may need to help with this one, but it
looks like to me that you have an error with some file
in the /usr/local/OpenVistA/vista directory. This is
probably where all your routines are stored, so that
won't likely help you much. But whatever the file,
the error was on line
The INDEX file... very interesting. I'll have to
check it out in the VPE data dictionary...
Thanks
Kevin
--- Gregory Woodhouse
[EMAIL PROTECTED] wrote:
For traditional cross-references, it's the ^DD
global and for new style
cross-references, the INDEX file. But you should
always edit
Norman,
Thanks for the offer. I have a drug file. But my file
#51 is completely empty. Is this propriatry? I don't
think I really have to have it, since we are not
dispensing drugs.
I am close to figuring out how all the drug files are
related. I have been able to:
1. Add a PHARMACY
The 3rd node is where a single line text message is placed. If it
exists, you can't use FM to delete the cross-reference's logic (i.e.
you can't delete the definition of the cross-reference). It does
double duty. It educates and warns with the text and its existence
acts as a lock. Here are
You guys are the greatest source of information!
I really appreciate it. Thanks
Kevin.Greg Kreis [EMAIL PROTECTED] wrote:
The 3rd node is where a single line text message is placed. If it exists, you can't use FM to delete the cross-reference's logic (i.e. you can't delete the definition of the
Greg Woodhouse wrote
Getting the lengh of a UTF-8 string is not entirely trivial, either,
because UTF-8 is a variable length encoding.
Actually, it is quite simple. You can just count the continuation bytes and
subtract from
the string length. Those are the only ones with 10 as the first two
There are a lot of nice features like multi-field cross-refences and
rec ord level execution (the cross-reference fires when the entire
record has been edited, not just the field), enforced uniqueness (if
desired), control of collation for individual subscipts, better thread
safey, text
Thanks Gary.
--- GARY MONGER [EMAIL PROTECTED] wrote:
Something's wrong. You might also check to see if
you have anything at
^DPT(DFN). The ICN is hanging on ^DPT(DFN,MPI).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Jim
Wheeler
Sent:
Hi Kevin,
I've got about 300,000 paients in the active ICN
index. 299,988 have a corresponding 0 node in ^DPT.
I'm running Cache on VMS.
After further research it appears that the AICN
index is outta wack. I'm guessing either something
bombed during the filing process or someone wrote a
buggy
Cameron,
You say to kill off the global, can you be a little more detailed on how
this is done on CACHE. Us newbies have limited knowledge and most of this
translates into Greek.
--- Cameron Schlehuber [EMAIL PROTECTED] wrote:
Kill off the %ZOSF global first before running ZTMGRSET for
Butch;
KILL works the same way in Cache as it does in MUMPS. There are some
settings that Cache has which may mean that you must be in the SYS
environment or that whole globals cannot be deleted. If this is the case,
you can easily remove teh contents of the global by this code;
S N=
26 matches
Mail list logo
