Somehow I convinced myself I had to create
it before I could edit. Thanks to Thomas and Greg I finally got it.. I’m
glad this group is so rich in resources.
Thanks,
thurman
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Holloway, Thomas (EDS)
Sent: Monday, June 27, 2005 7:17
AM
To:
hardhats-members@lists.sourceforge.net
Subject: RE: [Hardhats-members]
KIDS options
Thurman,
Create a Build Using Namespace <== this will
auto-build with everything. Not what you want.
Copy Build to Build
Edit a
Build
<== use this to create a new build and add individual components.
Transport a Distribution
Old Checksum Update from
Build
Old Checksum Edit
Routine Summary List
Version Number Update
Select Edits and Distribution Option: edit
a Build
Select BUILD NAME: PRC*5.1*85
Are you adding 'PRC*5.1*85' as a new BUILD (the 6289TH)? No// Y
(Yes)
BUILD PACKAGE FILE LINK: PRC IFCAP
PRC
BUILD TYPE: SINGLE PACKAGE// SINGLE PACKAGE
BUILD TRACK PACKAGE NATIONALLY: YES// N
NO <== at the VA we use this but you won't need it.
Edit a
Build
PAGE 1 OF 4
Name:
PRC*5.1*85
TYPE: SINGLE PACKAGE
etc, etc,
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse
Sent: Monday, June 27, 2005 8:41
AM
To:
hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members]
KIDS options
I suspect that you're using the option to create a build from a
namespace. This is a convenience for developers so that they do not have to
type in every component in a package "by hand". Just skip this step
and you should get an empty build to which you can add your components.
"Before one gets the right answer, one must ask the right
question." -- S. Barry Cooper
On Jun 26, 2005, at 11:35 PM, Thurman Pedigo wrote:
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. Everything
in this system has the MAW namespace. Now I wonder if I need to back the file
up under a different namespace. Perhaps that would drop all the extraneous
SORTS, OPTIONS, ETC…any thoughts?
thurman
thurman
Instead of trying to edit an existing build definition, you
should create a new one containing just the components you want.
"It
is a capital mistake to theorize before one has data."
On
Jun 26, 2005, at 10:50 PM, Thurman Pedigo wrote:
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 DON’T want them in the VistA system.
Am
I using the “edit” incorrectly? Or am I at he wrong place? Guess I
need to go back to the manual ;-).. I just can’t fund how to deal with
this configuration.
Thanks,
thurman
Edit a
Build
PAGE 3 OF 4
Name:
MAW*1.1*1
TYPE: SINGLE PACKAGE
-------------------------------------------------------------------------------
Build Components
SORT
TEMPLATE
(1862
INPUT
TEMPLATE (127)
FORM
(66)
FUNCTION
(11)
DIALOG
(0)
BULLETIN
(0)
MAIL
GROUP
(1)
HELP
FRAME
(1)
ROUTINE
(0)
OPTION
(598)
SECURITY
KEY
(0)
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 components
that are used in Vista. Just ignore what you don't need.
"Without
the requirement of mathematical aesthetics a great many discoveries would
not have been made."
On
Jun 26, 2005, at 9:23 PM, Thurman Pedigo wrote:
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 looking at
easily over a thousand options to delete. It would be nice to select the
options for deletion and do all at one operation.
Thanks,
thurman
|
