|
Again, I'm not sure if it will work, but if you look at the XML file in the compile folder previously mentioned, you could try removing all the IBM shipped commands. Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/14/2006 03:54:26 PM:
Michael, I see what you mean. I had not seen that the delete option was
unavailable.
Can you change the command to compile as you want, and then add the new ones? Jim -- Jim Essinger Senior Programmer/Analyst SLFIMA PO Box 1000 Fruitland, ID 83619 208-452-4058 x133 On 12/14/06, Michael Rosinger <mrosinger@xxxxxxxxx> wrote:"Jim Essinger" <dilbernator@xxxxxxxxx> wrote in message news:mailman.2762.1166121598.1743.wdsci-l@xxxxxxxxxxxxxxxMichael, Can you use the "Work with compile commands" to remove the ones youdon'twant? I believe you can add or remove all versions etc.Jim, I tried that. You can right-click on any command in the list. The ones supplied by IBM have the "delete" option in the context menu grayed
out.
The ones I added, however, may be deleted. Evidently the application
"knows"
which commands are supplied with it and which are user-defined. -- Regards, Michael Rosinger Systems Programmer / DBA Computer Credit, Inc. 640 West Fourth Street Winston-Salem, NC 27101 336-761-1524 m rosinger at cciws dot com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.