nt: Sunday, June 26, 2005 10:42 PMTo: hardhats-members@lists.sourceforge.netSubject: Re: [Hardhats-members] KIDS options 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
Of Gregory Woodhouse
Sent: Monday, June 27, 2005 12:02
AM
To:
hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members]
KIDS options
Instead of trying to edit an existing build definition, you should
create a new one containing just the components you want.
===
Gregory
, 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
: [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
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
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
]
[mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse
Sent: Sunday, June 26, 2005 10:42
PM
To:
hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members]
KIDS options
There is no need to do anything like that. If you mean to create KIDS
build containing only routine (not at all
