Español  |   中文  |   Français  |   English
Home  |  About DBDOC  |  Why Do I Need DBDOC If I Have...?  Print   Sitemap
GMCL




Find DBDOC at hundreds of sites worldwide!

Conectiv Energy | Detroit Edison Co. | Reliant Energy | Australian Paper | ExxonMobil Canada | Petro Canada | Talisman Energy UK | Huaneng Qinbei Power

Why Do I Need DBDOC If I Have...?

Why do I need DBDOC if I am converting to Composer®?

DBDOC has special features and reports for making the job of converting from WinCAD to Composer much easier:

  • Verify that your root user macro library works - DBDOC does the equivalent of a complete compile that will tell you if any shapes are missing from the library you plan to convert.
  • Find duplicate global output references - DBDOC will tell you about output references that are going to be converted to Copy 1, Copy 2 and so on, something nobody likes.
  • Find case-sensitive output references - DBDOC will tell you about output references that differ only in some letters being lowercase. If you miss these, you will have a major cleanup job ahead of you.
  • See also Why Do I Need DBDOC if I Have WinCAD? and Why Do I Need DBDOC if I Have Composer?.
Last updated February 10, 2010
DBDOC ©1996 - 2016 G. Michaels Consulting Ltd., all rights reserved. Unless noted otherwise the following are products, trademarks, service marks and/or registered trademarks of their owners and/or holders in the U.S. and/or other countries. MediaView, Microsoft, Visual Studio and Windows are owned and/or held by Microsoft Corporation. AutoCAD is a registered trademark of AutoDesk, Inc. MicroStation is a product of Bentley Systems, Inc. ABB, Batch B90, CADEWS, Composer, Tenore NT, Conductor NT Graphics, INFI 90, PCView, SODG, Symphony, WinCAD and WinTools are owned and/or held by ABB Group. RoviSys Turbo Lite Server is owned and/or held by The RoviSys Company. This website largely available under the terms of the AGPLv3.