Re: [foxboro] IACC Product and Integration with existing I/A tool s
- From: "Corey R Clingo" <clingoc@xxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 3 Feb 2005 11:20:38 -0600
I saw the information you refer to, but I just wanted to be sure, in light
of some of Alex's statements. Sounds like there is nothing physically
preventing you from using both ICC and IACC for edits, but Foxboro doesn't
recommend it. Reads from both are OK, however.
Corey
tom.vandewater@xxxxxxxxxxxxxx
Sent by: foxboro-bounce@xxxxxxxxxxxxx
02/03/2005 08:34 AM
Please respond to foxboro
To: foxboro
cc:
Subject: Re: [foxboro] IACC Product and Integration with
existing I/A tool s
Corey,
You said:
"I like to use iccprt to get configuration data out of the system. I have
several scripts that parse this data for various purposes. Even if I did
decide to use IACC for all my configuration, I'd still like to have this
capability. I suppose if the "ownership" of a CP is determined merely by
a
text file somewhere, as Doug suggests, it's easy enough to get around,
though even doing what he describes for a quick iccprt dump is more effort
than I'd like."
You may have missed it in all of these postings on this issue but
Iccdrvr.tsk is still supported if you are using IACC even without
switching
back to ICC so your iccprt scripts should still work. We, too, are
heavily
utilizing Iccdrvr.tsk functionality.
Read the last line of the anonymous posting below:
> Did you previously use ICC or FOXCAE?
Yes, ICC, FoxCae and IACC hold no secrets for me, it's my job for over 6
years. ICC is great for changing/building a single block but otherwise
useless in my work. FoxCae is great for generating large databases, it has
a
very fast and reliable database, but it's a complex, unintuitive program.
IACC is different and has its issues, but has some definitive advantages
as
well. "Iccdrvr.tsk is also still my good friend."
Tom
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
