I tried creating a new build. When I get
to page three it gives me the same configuration. Perhaps I need to just try it
and see if it moves the files over. I think it will – maybe not. I have
it backed up. Just wanted to see what the thinking was. I’m (obviously)
total novice with KIDS.
Instead of trying to edit an existing build definition, you should create a new one containing just the components you want. ===Gregory Woodhouse[EMAIL PROTECTED]"It is a capital mistake to theorize before one has data."--Sir Arthur Conan Doyle On Jun 26, 2005, at 10:50 PM, Thurman Pedigo wrote:Par
Part of my concern relates the what
happended when I had to move (KIDS) the PROTOCOL file from VistA
to my native FileMan system. That KIDS surprisingly brought over a ScreenMan
form and option. The screenshot below shows 1860 SORT templates. If I enter
that bank they are all there. I DO
There is no need to do anything like that. If you mean to create KIDS build containing only routine (not at all uncommon), just fill in the routines you need and save the form. KIDS is a general purpose utility for distributing software in Vista, so it needs to support all the various kinds of comp
I am working on doing a KIDS transport of existing FileMan files into VistA. As I create these KIDS builds I am struck by the
number of options in each build – options which I have no need. Is there
a way to erase the excess options without a “@” kill of each
individual option? We are looki
I suspect that if vim works properly, then the same should be true of
^XGFDEMO. Are the IO* variables being set up in a way that looks
reasonable? BTW, i use vt220 or vt320 almost exclusively at work, but
the subtype is still usually vt100.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"The most
Well, no.
An xterm is a VT compatible terminal emulator.
C-VT100 is the terminal type for a particular VT terminal.
Though maybe yes.
All I said above but as I recall, the VT-100 was a particularly
stupid dumb terminal. Perhaps a VT-220 or VT-320 would have the
capabilities you want. The mismat
$TERM --> xterm
IOST --> C-VT100
A mismatch. What do think I should do to get this
working?
Thanks
Kevin
--- Gregory Woodhouse
<[EMAIL PROTECTED]> wrote:
> If XGFDEMO doesn't work, there's probably an issue
> with your terminal
> type settings. The XGF library is basically the
> Kernel equi
I agree with you in concept. In today's world of SAN and NAS and TB files
one has to take this all in consideration. I will have to reconsider my way
of thinking. What I am still hesitant about is the advantages and
disadvantages of having all your data in one massive file spread over many
spind
