It is now possible to define a section (named EDIT_BOM) in the SCHEMA\Tables2.DFL file for declaring the fields to be displayed in the Edit BOM ... dialog.
This section management is supported by Administrative Tools.
(see main help on EditBOM dialog for details)

A new logic has been implemented, that avoids any change of the native CAD order.

With R10, there exists only two order conditions:

1. the native CAD order, with no Absolute BOM Position Numbers
2. the assigned Absolute BOM Position Numbers order

Since of this new logic, it is now possible, when the native CAD order is still applied, to sort the BOM items by double-clicking on the ID/CONFIG/DESCRIPTION/… column’s headers and to apply the new order only as Absolute BOM Position Numbers

Cleaning-up the Absolute BOM Position Numbers will RESTORE the native CAD order

If existing, the LST\PARENT_CHILD_MAKE_BUY.LST ( localized for each language ) is loaded for the MAKE/BUY values choise list; if not existing, it is loaded the LST\MAKE_BUY.LST

This new option allows the creation of Generic Documents records as BOM Items.
The Generic Documents extensions that will be managed as BOM Items can be defined in the sub-option File Extensions.

For example, with the settings as in the above picture, only files with extensions equal to .DWG, .DXF and .ME will be managed as BOM Items.
For documents that are in match with the File Extensions option, the default MAKE_BUY attribute is MAKE.
For drag&drop operations, the PARENT_CHILD_MAKE_BUY attribute will be assigned to MAKE as well.

The Briefcase functionality is now supported on the x64 platforms by using the out-of-process DBWorks Standalone x32 server.
The out-of-process DBWorks Standalone server is needed since of the lack of 64-bit ODBC drivers for the MDB database, used in the Briefcase files for the snapshot of the database structures.
The LST\SYSTEM\Briefcase.vbs script has also been modified for the above reasons.

By using this script is possible to customize the double-click action, that by default is the Open of the document.
(see CommandShell help module for details)

Better UI feedback when in Open For Updating mode

The chosen date/time format is now displayed in all the grids.

When checked, DBWorks will never popup any notification dialog when an in-memory read-only component has been modified by another designer.
Only a tooltip will appear on the screen for remembering that a component needs to be reloaded.
The DBWorks Toolbar Reload button will become enabled, and it will be possible to reload all the notified components at any time.

The User Interface is now compliant with the rest of the dialogs in DBWorks; in particular:

• the next CONFIGURATION_REVISION value is assigned with one button; the YELLOW background indicates the modified rows
• Visual cues are supported
• The REVISIONS.DESCRIPTION is now displayed
• Multiple selections are allowed

If checked, for documents with only one configuration, DBWorks does not overwrite the CONFIGURATION_REVISION value with the REVISION value – for documents with two or more configurations, the option is not active, because DBWorks never overwrite the CONFIGURATION_REVISION value in such cases

The cut-list records are now managed by the Link-mode, so avoiding troubles when approving or checking-out-in the Part record.
No Link-Mode field alignment is applied to cut-list records.
By adding a condition like *.CUTLIST to the [X] Track derived parts→[X] Avoid linking of documents like … option , it is possible to disable the Link-Mode for cut-list records

From the Advanced Filter you can output the results of a query to a .csv file (Comma Separated Values), that is a text format supported by Microsoft Excel.
To export the results, click the button

and select a file location.
If you have an application associated to .csv files on your computer, the file is opeed to display the results. In this case Microsoft Excel displays the results.

To set the fields, you can use the Admin Tools:

The option, already available for the SolidWorks platform, is now available also for the Inventor platform.
If checked, when pressing the Shift key while “saving as”, DBInventor will launch the native Inventor ‘Save As’, so allowing to choose an export format (like IGES, DXF, etc.)

Sets the DisplayName of an Inventor Document by using Inventor Apprentice – the command is implemented only in DBInventor Integrated version.
(see CommandShell help module for details)

Any Working Set operation is executed in the DBW Feature Manager search grid, without opening the Browser for such purpose.
The Working Set is saved/loaded on next openings.
The full set of Working Set RMB operations is also available from the DBW Feature Manager grid.

It is now possible to insert a text value in a field with the same syntax of a Variant Note.
The text value will be dynamically resolved:

• at visualization time
• at file properties write time

When checked, the ID is checked across Part and Assembly documents in order to avoid any duplication.
For example, with the option UNCHECKED, a part with a specific ID can exists together with an assembly with the same ID; with the option CHECKED, a part can never have the same ID of an assembly.

If checked, all the SPT defined buttons are visible also when in View mode.

A RMB popup menu is now available in the Used By grid when the Data Input form is displayed for the View or Edit functionalities.
Note: since of the Modal state of the currently displayed form, not all the functions in the popup menu are available

When checked, it will not be possible to create a Major Revision.
The option can work only with the OnNewRev.LST script activated, which will always receive the parameter @NEXT_REVISION_TYPE=MINOR

Any DBWArm action is now logged in the EVENT_LOG table.

When checked, the Link Mode will also consider any Generic Documents that is a Parent of Parts/Assemblies.
A typical usage of this option is for keeping aligned the revisions of parts that have been created for migrating legacy file formats into 3D file formats

When editing a Part/Assembly document record, DBWorks keeps always updated also the DOCUMENT.propertyName drawing’s properties. When used with SolidWorks 2008 or newer, and with properly designed drawing templates, this feature allows to avoid the Drawing refresh on document approval; drawings opened in View-only mode will show the updated data for any $PRP drawing annotation linked to a DOCUMENT.xxx property.

When checked, only the lengths/dimensions/equations assigned in the list Data Input→ More sketch/dimension/equation→field data input are automatically calculated at every save, so skipping any mass property calculation The mass property can always be acquired with the manual process.

RMB→Plot on a Search Grid’s Multiple Selection ( as well as on many other Grids ) is now supported

When checked, the eDrawings plots are created with Color and Shade enabled.

The static preview of all documents maintain now the correct aspect ratio.

A new RMB functionality is available for adding all the Parent Projects of a document to the current Projects Selection.

When the DBWShell(“Download”) is called with the parameter QUICKCHECK, the output parameter @OKDOWNLOAD is set to 1 if the file’s last modified date is newer than the database LAST_MODIFIED_DATE for the passed Unique ID, offseted with the value found in the DBW_COMPANY_INFO::DBW_TIME_ZONE_OFFSET field.
When used with this parameter, the DBWShell(“Download”) command makes no access to the remote file system for the exact file system date and size.
(see CommandShell help module for details)

Documents that have invalidated (due to a new approved revision) a parent “dirty” assembly are now highlighted in the Project Tree.

The function, available from the Tree interface, collects into a Working Set all the child documents that have been marked as “dirty”.

The function, available from the Tree interface, collects into a Working Set all the child documents that created the “dirty” condition on the currently selected parent assembly.

Up to three different file outputs, with separate parameters, are now supported.
It is now also possible to automatically append the generated output file as a child generic document of the processed document.
Output file names no more contains the .SLD*. extensions.

On RMB you have the list of created output for the current revision. In the Previous revisions tab you can find other revisions outputs.

Adds an attachment to the currently selected document or to the passed unique_id
(see CommandShell help module for details)

Writes in the %TMP%\DBWorks…LOG the passed message string; the function may be useful for debugging custom applications written over the DBWorks API
(see CommandShell help module for details)

It displays the Tree Page’s Project Tree
(see CommandShell help module for details)

New commands to manage messaging inside the DBWorks environment
(see CommandShell help module for details)

Saves the current Browser state and selections in the Users\userID folder
(see CommandShell help module for details)

Every .LST/.VBS script receives now the parameter DBWorksIsx64, with value TRUE if invoked from an x64 DBWorks

It is now possible to convert from .DOC/.DOCX/.XLS/.XLSX/.PPT/.PPTX/.MBX into PDF.
Files created with a version of Office older than Office 2000 are not managed

The DWG to PDF conversion considers now every .CTB, .SHX, etc. Autocad file that is found in the shared ..\PAR sub-folder

Returns the state for batch executions from a Working Set
(see CommandShell help module for details)

DBWorks manages now correctly the BOM quantity in cases where not all the components are marked in SolidWorks as ‘Excluded from BOM’.
The logic is now that if ALL the component’s instances are marked as ‘Excluded from BOM’ in SolidWorks, then the parent-child relation has the quantity equal to the number of instances, and the PARENT_CHILD_MAKE_BUY attribute set to NO_BOM; in case at least one component instance is NOT marked as ‘Excluded from BOM’ in SolidWorks, then the parent-child relation has the quantity equal to the number of instances not ‘Excluded from BOM’, and the PARENT_CHILD_MAKE_BUY attribute is then reset to blank.

When checked, DBWorks, at each Edit record, updates the SolidWorks Configuration::Description property with the value contained in the DESCRIPTION field, and the SolidWorks Configuration::Comment property with the value @UNIQUE_ID=uniqueID
The action is executed when the SolidWorks model is opened as well as when it is closed.
The automatic assignment is NOT executed if any of the SolidWorks@ConfigurationProperty@Description or SolidWorks@ConfigurationProperty@Comment is imported through the CUSTPROP.TXT
This new option is typically used together with the installation of DBTools (see na-ips.com for details on DBTools), and together to the setting of both the: Configurations→[X] Manage 'Add/Remove Configuration' event→[X] Use 'DataEntr.LST' on 'Add Configuration' event
Since of the above settings, when the option is checked, the Dataentr.LST script is also ALWAYS launched even if a specific configuration is not a valid configuration as per the configuration’s filters settings.
This will allow the Dataentr.LST to take control over the name to assign to the newly added configuration, no matter of the configuration’ name entered by the user

Virtual Components are now supported – DBWorks R10 ignores any Virtual Components until they are saved externally as “real” component files.
When saved as “real” component files, all the Save Wizard scripts are applied.

The SW default templates settings are now used for the DBW Insert New Component functionality.

The DBWShell(“swSaveAs”) command has been extended in order to support all the PDF options available in SolidWorks.
(see CommandShell help module for details)

If checked, Standard Parts will never be deleted when in Open for Updating mode

An additional Tree Control ( named Sub-Tree ) can now be displayed in the Tree Page for showing the Child and Parent trees. The Sub-Tree is enabled through the option: Options→User Interface→Tree→[X] Populate Child/Parent Tree in the Sub-Tree.

The “[X] Do not show this message again” check-box values are now permanently stored in the User registry, so their value is maintained across multiple sessions of DBWorks/DBInventor
To force the message boxes to be displayed again, the SHIFT key must be kept pressed while invoking the function

After opening the document folder, the current document is now selected in Windows Explorer.

The MS Office files (from Office 2000 to Office 2007) can now be correctly viewed when the “Options→User Interface→Preview→[X] Full preview of generic documents” is checked.
DBWorks converts “on the fly” the MS Office documents in PDF files, and uses the PDF viewer for them. The conversion does not need MS Office to be installed on the workstation.
The “User Interface→Preview→[X] Create temporary files in a different directory” can be set for the alternate folder where to create the .PDF conversions.

The new position code 4 means “on icon” for the Tree and “left side” for the Grids.
(see main help on VisualCues for details)

R10 allows the enabling/disabling of Workflow States from an already started Workflow Process.
This new feature allows the rest of a Workflow to be processed based on the decision of some key user, responsible for routing the current Workflow process through specific states. (see main help on Workflow for details)

If checked (default CHECKED), the script OnSendWorkflowNotificationToUsers.LST will be launched at every Workflow approval

This new mandatory fields ( VARCHAR(10) ) are now managed in the DBW_WORKFLOW_ECO and DBW_WORFLOW_ECR tables.
They are filled with the value ‘CLOSED’ when an ECO/ECR is approved
The ECO list in the OnSubmitToWorkflow.LST can be filtered on this field for avoiding to display already closed ECOs

Multiple operations like the checkout/checkin of multiple records are no more destroying any existing Working Set.