PLC Database File Editor

[Anonymous]

In the PLC Database File Editor, when I select the I/O module to edit, I get the following error: "PLC Database - Additional Field Required: We have detected that the 'Category' field is either empty or missing for the selected table. This field is required, in order to use the PLC Database, it must be updated. Would you like to update the database now?" Then I select Yes and it brings up a PLC Database Migration Utility window. I click OK and nothing happens. Any suggestions?

Mark

[Anonymous]

Mark,

The table structure changed in the PLC database for 2009. Is sounds like
you have a pre 2009 PLC database that you are using in 2009. As you have
seen, it will try to convert the database. After the conversion, you should
be able to edit your modules. Are you not able to edit some of the modules
after the conversion? If so, which ones are you having trouble with, and
were they created by you, or were they shipped with a previous version of
AutoCAD Electrical?

Thanks,
Mike

wrote in message news:5981588@discussion.autodesk.com...
In the PLC Database File Editor, when I select the I/O module to edit, I get
the following error: "PLC Database - Additional Field Required: We have
detected that the 'Category' field is either empty or missing for the
selected table. This field is required, in order to use the PLC Database,
it must be updated. Would you like to update the database now?" Then I
select Yes and it brings up a PLC Database Migration Utility window. I
click OK and nothing happens. Any suggestions?

Mark

[Anonymous]

We did upgrade from 2006 to 2009. Is there somewhere that I can check to see which database is being used? I attached an image file showing the window that pops up after the error message. Once I click OK, I'm back where I started and receive the error once I try to edit. I'm not able to edit any of the modules, and they are all from AutoCAD Electrical. Is there possibly something in the ACE_PLC.MDB file that I need to edit?
Thanks

[Anonymous]

Mark,

The database being used is listed in the PLC Database File Editor dialog
towards the top (see attachment). So from what I am reading, you get this
with all modules, or if not can you tell me which ones in particular that
you are having trouble with?

Thanks,
Mike

wrote in message news:5981702@discussion.autodesk.com...
We did upgrade from 2006 to 2009. Is there somewhere that I can check to
see which database is being used? I attached an image file showing the
window that pops up after the error message. Once I click OK, I'm back
where I started and receive the error once I try to edit. I'm not able to
edit any of the modules, and they are all from AutoCAD Electrical. Is there
possibly something in the ACE_PLC.MDB file that I need to edit?
Thanks

[Anonymous]

Yes I get the error with all modules. We have our library stored on a server, and the path doesn't have which database, but this folder was created when AutoCAD 2009 was installed. \\2003server\Eng\Library\Elec Symbol Library\AeData\plc\ACE_PLC.MDB.

Thanks,
Mark

[Anonymous]

Mark,

Check to make sure you have write privileges to the database file that is
being edited. That is one reason you might get the results you are getting.

Regards,
Mike

wrote in message news:5981808@discussion.autodesk.com...
Yes I get the error with all modules. We have our library stored on a
server, and the path doesn't have which database, but this folder was
created when AutoCAD 2009 was installed. \\2003server\Eng\Library\Elec
Symbol Library\AeData\plc\ACE_PLC.MDB.

Thanks,
Mark

[Anonymous]

That fixed it. Thanks Mike!

[Anonymous]

The ace_plc.mdb is on my local hard drive and I do have write permissions, but I'm having the same problem. I've also tried running the Migration Utility on the database, but the utility says "Source file type is invalid."

[Anonymous]

So you are getting the "...update the database now?" message box and you
are saying yes to update the database, then when you click on a module and
it asks you again? If so, does it seem to happen for all modules or a
specific set of modules?

Thanks,
Mike

wrote in message news:6025873@discussion.autodesk.com...
The ace_plc.mdb is on my local hard drive and I do have write permissions,
but I'm having the same problem. I've also tried running the Migration
Utility on the database, but the utility says "Source file type is invalid."

[Anonymous]

Yes, that is correct. It occurs for all module series and type.

[Anonymous]

Ok, I want you to try the following:

1. Copy the ace_plc.mdb file to a location you know you have full rights
to, such as your user folder (by default, in XP that would be "C:\Documents
and Settings\\Application Data\Autodesk\AutoCAD Electrical
2009\R17.2\enu\Support\User")

2. If you didn't use your user folder in step one, then add the folder to
the Support File Search Path in the Files tab of the AutoCAD options dialog

3. Rename the orginal file so that Electrical can't find it (like
ace_plc.mdb.org)

4. Restart Electrical and go to PLC Database Editor and see if you get the
same issue.

Thanks,
Mike

wrote in message news:6030104@discussion.autodesk.com...
Yes, that is correct. It occurs for all module series and type.

[Anonymous]

My database is in C:\Program Files\Autodesk\Acade 2009\Doerfer\AeData\Plc, where I have full rights, but I tried moving it to my User folder. I can see at the top of the PLC Editor that is does use the database in the new location, but I still have the same issue.

[Anonymous]

My PLC database file is roughly 40 meg. It zipps down to 3 meg. We can
receive a file as large as 10 meg via email. So if you haven't added too
much to it, you should be able to zip it and send it to me. If you want,
you can zip up your PLC database file and send it to me directly at
mike.spitzer@autodesk.com, and I will take a look at it.

Regards,
Mike

wrote in message news:6030413@discussion.autodesk.com...
My database is in C:\Program Files\Autodesk\Acade 2009\Doerfer\AeData\Plc,
where I have full rights, but I tried moving it to my User folder. I can see
at the top of the PLC Editor that is does use the database in the new
location, but I still have the same issue.