When I create a new report, whether it be Drawing List Report or Panel BOM Report, the justification settings are following the table style settings instead of the settings from the report .SET file. It has been working fine for years until just recently. The table style for my Panel BOM Report is "ACE_TABLE_1" (see attached "TableStyle.jpg").
My bompnl.set file is set so the DESCRIPTION column justification is middle left (see attached "bompnl.jpg"). The preview in the Report Generator dialog box looks correct as well. But when I place the table on the screen the DESCRIPTION column justification is middle center, which matches the table style (see attached "Report Table.jpg"). I can actually change the table style justification to middle left, and it will update the data cells in the table to middle left instantaneously.
I have tried:
Deleting the bompnl.set file and recreating it from scratch
Deleting the table styles and recreating them in my template
Starting a brand new project with a new drawing using the newly created table style and set file
Also, this is only happening to my computer. It works fine on the other 7 computers in my office, and we all use the same report .SET files from a shared network location. I can't think of any settings I changed or files I might have deleted to make it override the .SET files settings. I'm not sure if a program repair or reinstall would help or not, but I'm thinking that's my next move. Any help is appreciated. Thanks
I will report this and make sure it gets logged. Sounds like there is a conflict between the table style and the AutoCAD Electrical settings.
Sorry for this inconvenience.
Regards,
Pat Murnen
Hello Holden,
I could reproduce this issue on our side. We have registered this case at our end.
Thanks for reporting & sorry for inconvenience caused.
This just started happening to me as well, any word on the fix? Can I reinstall ACADE without SP2?
Very very frustrating.
Was a true fix for this issue ever released by Autodesk without having to unistall SP2? Or is SP2 the culprit?
I never received an update on a fix for that issue. We are on subscription and the next year's release solved the issue. I have never had that problem since.