RE: [Hardhats-members] KIDS options

Sun, 26 Jun 2005 23:38:15 -0700

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 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf 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 Woodhouse

 

"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:



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) 

From: [EMAIL PROTECTED] [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 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.

 

===

Gregory Woodhouse

 

"Without the requirement of mathematical aesthetics a great many discoveries would not have been made."

-- Albert Einstein

 

 

 

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




 



 

Reply via email to