Martin,
I believe that you have run into a logged issue. Try this for me. Type the
following at the command line:
!GBL_wd_DocSetBase
This will most likely return to you the location of the Support folder in
your Documents and Settings folder. It may look something like this:
"C:/Documents and Settings/spitzes/Application Data/Autodesk/AutoCAD
Electrical 2006/R16.2/enu/Support/"
In this folder, you should find a file called WDMBBLKS.BSF. This file is
the block settings file and contains among other things, the information
that maps the terminal descriptions to the terminal blocks. The issue is
that when you move your data for your PLCs (in this case you are sharing it
on the network), Electrical is still looking for that BSF file in your
Documents and Settings support folder. If you have made any changes to the
Terminal Block Settings in the PLC Database Editor, these settings will be
saved to this wdmdbblks.bsf file. When you do a new install on a new
computer for example, the installed file will not have your additions or
modifications in it, so you will get an "Undefined Terminal Types" error
when you try to edit a module that uses the additional terminal types that
you defined. The work around is to make sure that the BSF file that you
have local matches the BSF file that you are sharing on the network (if the
file is on the network) or that matches the file you had on your old
computer. You can copy it over, but I would suggest making a backup first.
You may need to copy this file to each users computer in order for them to
be able to edit these modules as well. This is a logged issue and is being
looked into. Hope this helps.
Mike
wrote in message news:5042189@discussion.autodesk.com...
DUH!!! Bad Guess! Since we use profiles, the search paths are the same. I
suspect that this file wasn't designed to be used or modified across a
network. I've noticed this issue before when someone else attempted to edit
the file and had the same issues. The error message is regarding "Undefined
Terminal Types", which is an error itself, as the terminal types are
actually all there.