Well, I guess a good night's sleep helps :-) I tore into the problem
again this morning and noticed that the ACTION definition specified
"EXEC_STRONG" instead of "EXEC_STRING"; sure enough, that was the
kicker. The interesting thing is that this *wasn't* a problem before; I
guess it's because of the duplicate definitions I mentioned (there is a
WireTool for the other office, and it must have taken precedence).
My original message should be coming around soon enough -- I haven't
even seen it yet! -- and so I won't bother to include it here.
Sheepishly yours,
:-D
-- David Thorburn-Gundlach dtg@cae091.ed.ray.com,david@bae.uga.edu Raytheon 508/440-2016 or 508/440-2317