• .NET 2.0 must be installed
• If working with SolidWorks, SolidWorks 2007 is the minimum version supported

Any given .NET assembly has the following major characteristics:

• file name
• assembly name
• assembly module name
• assembly namespace

The naming convention for the .NET framework was always simple: all three are the "same".

• file name: System.Windows.Forms.dll
• assembly name: System.Windows.Forms
• assembly module name: System.Windows.Forms.dll (the original file name embedded into assembly file header)
• assembly namespace: System.Windows.Forms

Microsoft has broken it's own rule with the way how Visual Studio 2005 generates interops: the file name always has prefix "interop." and does not match any more the assembly namespace. What leads to the situation when it is not possible to reconstruct the file name from the assembly namespace (this is what the DBWCSSUI engine does).

The solution is to use the DBWCSSUI explicit loading directive //css_ref : this resolves the loading problem.

About how to reference the namespace from the code, in C# it is resolved through the using directive; VB equivalent is Import.
Thus if you want to use, for example, System.Windows.Forms your code needs to have Import System.Windows.Forms.
In addition to this, VB compiler has it's unique feature imported namespaces which means that you can nominate namespaces to be used not from code but on the compiler level.
This is the reason why you do not have to have Import System.Windows.Forms in the code if you are inside of the VB project: nice feature but inconsistent and creates some confusion.

DBWCSSUI does not pass any extra compiler directives thus you must have Import <namespace> in code if you want to use a particular namespace.

As a final note, renaming of the assembly file is not a very good idea in general as it creates mismatch between Assembly file and module name. Some applications may refuse to load such assemblies.

CacheBaseDir: The root directory for caching the local script compilation results.

DownloadBaseDir: The root directory for downloading (caching) all remote scripts.

CodeProviderDll: Location of the VB compiler assembly. This value is passed at run time to the CS-Script engine through it's configuration file.

DebugMode: Boolean flag, which indicates that the script should be compiled with debug information included.

SimpleRemoteCaching: Boolean flag, which indicates when the remote script dependency files (assemblies and importable scripts) have to be analysed for changes.

• True: Files are analysed only if the primary remote script file is changed. This is the quickest algorithm as it does not require reading the remote script every time it is executed.
• False: Files are analysed every time the primary remote script file is executed.

VSBaseDir: Root directory where all temporary C# and VB projects are generated.

VSCleanResx: Boolean flag, which indicates that any automatically generated .resx files (for temporary VS project) should be deleted on after closing the IDE.

VSUpdateIncludesOnClose: Boolean flag, which indicates that new //css_imp should be automatically injected to the script file after closing the IDE. The injection is usually triggered by adding .cs/.vb file to the project by developer. New directives are marked with "//auto-generated" comment.

VSUpdateRefsOnClose: Boolean flag, which indicates that new //css_ref should be automatically injected to the script file after closing the IDE. The injection is usually triggered by adding assembly references to the the project by developer. New directives are marked with "//auto-generated" comment.

For each "standard" script ( *.LST or *.SPT ), DBWorks 2007 looks if a .NET version exists in the same directory.

The .NET version has the naming convention:

• <original script name>.VB for a VB.NET script
• <original script name>.CS for a C# script

The following is an example of OnOK.LST.CS:

//css_reference MW.DLL;
using System;
using System.Drawing;
using System.Windows.Forms;

public class DBWDotNet
{
	static public string Main( 
		string ApplicationName,
		string ModuleName,
		string ConnectionDSN,
		string ConnectionUID,
		string ConnectionPWD,
		string ConnectionDBMSName,
		string ConnectionORACLE_SERVER,
		string ConnectionORACLE_SCHEMA_OWNER,
		string ConnectionBomDSN,
		string IsInBatchOperation,
		string CurrentDocumentBatchOperationIndex,
		string BatchOperationDocumentsCounter
	){
		MW.DBWLib.Initialize(ApplicationName,ModuleName,ConnectionDSN,ConnectionUID,ConnectionPWD,ConnectionDBMSName,ConnectionORACLE_SERVER,ConnectionORACLE_SCHEMA_OWNER,ConnectionBomDSN,IsInBatchOperation,CurrentDocumentBatchOperationIndex,BatchOperationDocumentsCounter);
		
		String fileName;
		fileName = MW.DBWLib.DBWInput("FILE_NAME");
		MessageBox.Show("FileName=" + fileName);

		MW.DBWLib.DBWOutput("@OKDATA","1",MW.DBWLib.ForWriting);

		String description;
		description = "Created By OnOK.LST.CS";
		MW.DBWLib.DBWOutput("DESCRIPTION",description,MW.DBWLib.ForAppending);

		MW.DBWLib.Terminate();

		return "";
	}
}

Looking at the above script, you can see the following features:

1. the header must contain the //css_reference MW.DLL directive, for using the DBW standard script library
2. the main class must be named DBWDotNet
3. the entry point must be named Main and declared as the above sample; the self-explaining parameters are passed from DBWorks to the script at run time
4. each call to the DBW standard script library must be prefixed with MW.DBWLib.
5. all the variables must be explicitly declared
6. the very first call to the DBW standard script library must be the MW.DBWLib.Initialize , passing the parameters as shown in the above example; the Initialize calls internally the DBWInit(TRUE)
7. the very last call to the DBW standard script library must be the MW.DBWLib.Terminate()
8. all the methods of the MW.DBWLib class have the same syntax as documented in the standard DBWorks Help file, at the Programming DBWorks chapter

The same example shown above can be written in VB.NET as follows:

'//css_reference MW.DLL;
Imports Mechworks
Imports Microsoft.VisualBasic

Public Class DBWDotNet

	Public Shared Function Main(ByVal ApplicationName As String,ByVal ModuleName As String,ByVal ConnectionDSN As String,ByVal ConnectionUID As String,ByVal ConnectionPWD As String,ByVal ConnectionDBMSName As String,ByVal ConnectionORACLE_SERVER As String,ByVal ConnectionORACLE_SCHEMA_OWNER As String,ByVal ConnectionBomDSN As String,ByVal IsInBatchOperation As String,ByVal CurrentDocumentBatchOperationIndex As String,ByVal BatchOperationDocumentsCounter As String) As String
		MW.DBWLib.Initialize(ApplicationName,ModuleName,ConnectionDSN,ConnectionUID,ConnectionPWD,ConnectionDBMSName,ConnectionORACLE_SERVER,ConnectionORACLE_SCHEMA_OWNER,ConnectionBomDSN,IsInBatchOperation,CurrentDocumentBatchOperationIndex,BatchOperationDocumentsCounter)

		Dim fileName as String
		fileName = MW.DBWLib.DBWInput("FILE_NAME")
		MsgBox("FileName=" & fileName)

		MW.DBWLib.DBWOutput("@OKDATA",1,MW.DBWLib.ForWriting)
		if ucase(right(fileName,7))=".SLDPRT" then
			Dim id as String
			id = left(fileName,len(fileName)-8)
			Dim description as String
			description = id & " - Created By OnOK.LST.VB"
			MW.DBWLib.DBWOutput("DESCRIPTION",description,MW.DBWLib.ForAppending)
		end if

		MW.DBWLib.Terminate()

		return ""
	End function

End Class

Looking at the above script, you can see the following features:

1. the header must contain the directive ' //css_reference MW.DLL; ( a single apex, a space, then the //… ) , for using the DBW standard script library
2. apply the same rules described for the .CS script

The UserProcessDocument function, necessary to the DBWWalkTree functionality, it is supported by creating a special module named:
DBWWalkTree_UserProcessDocument.VB
with a template like:

' //css_reference MW.DLL;
' //css_reference MechWorks.Interop.DBWAlone.DLL;
Imports Mechworks
Imports Microsoft.VisualBasic

Public Class DBWDotNetUserLib
	Public Shared Function UserProcessDocument( ByVal uniqueId As String ) As String
		MsgBox(">>UserProcessDocument<< uniqueId=" & uniqueId)
		return "0"
	End function
End Class

The function UserProcessDocument is invoked by the MW.DBWLIB.DBWWalkTree for allowing the programmability of the actions on each document being processed.

DBWShell("FileZip <command> <file path>")

DBWShell("FileUnZip <zip file path> <output folder>")

DBWShell("SetPrimaryDatabaseTables <permanent> <DOCUMENT table name> <REVISIONS table name> <PARENT_CHILD table name>")

<permanent> [0/1] if 1, the primarty tables are pemanently set to the new names (useful for starting a Standalone Client on a new primary tables set)
if 0, the table will be reset as soon as the script terminate its execution

When the Primary Tables are different from the standard ones, the DBWorks Browser shows a notification in it’s title

Example

DBWShell("SetPrimaryDatabaseTables 0 DBW_ASBUILT_DOCUMENT DBW_ASBUILD_REVISIONS DBW_ASBUILT_PARENT_CHILD")

The following command resets the Primary Database Tables to their original values

Syntax

DBWShell(“ResetPrimaryDatabaseTables”)
		

Syntax

EMail <action> <parameter> <value>

Parameters

A new command GetTreeParentProject is available in the DBWShell interface.
The command returns the Unique ID of the nearest Parent Project in the current Tree structure.
When used with no parameters, it returns the nearest Parent Project Unique ID of the currently selected item in the Tree. When invoked passing a Unique ID as parameter, it first tries to select a document in the current Tree with the Unique ID equal to the one passed as parameter, then returns the nearest Parent Project in the Tree structure.

See CommandShell documentation for details.

This script is fired when dropping a set of files/documents on a target document.

Please refer to DBWShellCommand documentation for details.

It allows to customize the text that is displayed in the label of the Preview window of a document.

Please refer to DBWShellCommand documentation for details.

The ShowConfirmationDialog command has been enhanced for supporting the deletion of records and files, in the same way the user interface does.

Please refer to DBWShellCommand documentation for details.

• Document Page grids, if the Document Page is the current page of the Browser
• the search grid of a DBW Feature Manager window

Please refer to DBWShellCommand documentation for details.

A new optional parameter is available for passing the name of a field that will be displayed when the Data Input Form will be opened. Due to this is possible to change the default tab shown when dialog is displayed.

Example

call DBWShell ("EditRecord 45 1 CATEGORY3")

Please refer to DBWShellCommand documentation for details.

When called with no parameters, and if a Tree control was activated with a valid selection, it displays the UI Create a new Bom Item dialog.

Please refer to DBWShellCommand documentation for details.

For the PDF case only, the command applies the setting of the option Plot setup→Plot multiple sheets

Please refer to DBWShellCommand documentation for details.

• @IS_DERIVED_CONFIGURATION (Input)
  When the @CONTEXT=ADD_CONFIGURATION, a new parameter is passed to the Dataentr.lst for understanding if the current configuration is a derived configuration or not.
• @NO_SAVE_ALL_CONFIGURATIONS=1 (Output)
  If returned from the Dataentr.lst with value "1", DBWorks will avoid to save all the configurations automatically, even if the relative option is set

Please refer to DBWShellCommand documentation for details.

Starting from sp1.0 (planned for summer 2007) DBWorks 2007 will be installable in a special edition for running with SolidWorks 2007 x64 edition.

DBWorks can be run under Vista Operating System.

When checked, DBWorks will apply the new material (selected through the DBWorks Material Editor) to each configuration. DBWorks will also coherently update the Custom Properties for each configuration.

The option emulates the behavior of the following SolidWorks Edit Material Property Manager option:

The Dataentr.LST script (Save Wizard) can now output, if needed, the following parameters:

SolidWorks@ConfigurationProperty@Name
SolidWorks@ConfigurationProperty@Description
SolidWorks@ConfigurationProperty@Comment
SolidWorks@ConfigurationProperty@AlternateName

Example

Sub main()
	…
	…
	DBWOutput "SolidWorks@ConfigurationProperty@Name","MyNewCfgName",ForAppending
	…
End sub

The current configuration will be renamed as

The Summary Info properties can now be imported by declaring the following identifiers in the CustProp.txt ( or CustProp_Insert.txt ) file:

"SW_Title"
"SW_Subject"
"SW_Author"
"SW_KeyWords"
"SW_Comment"
"SW_SavedBy"
"SW_CreateDate"
"SW_SaveDate"

Example

CustProp.txt

DESCRIPTION	"SW_Title"
NOTES		"SW_Comment"

Please look at the Behavior Changes section for the changes applied to the List Locked Files functionality.

The following options:

Disable Assembly grid

Disable Parts grid

Disable Drawings grid

Disable Generic Document's grid

controls now the existance of the Assembly, Part, Drawing and Other Documents tabs in the Tree Page’s Grids area

A new tab named Configurations shows all the configured distinct records of the currently selected document:

The list of displayed fields is dynamically exchanged between the list for the Part type documents and the Assembly type documents, depending from the currently selected document type.

It is now possible to display custom query tabs in the Tree Page.

DBWorks will display as many tabs as the number of scripts .LST with the prefix OnCustomQueryTab_

Each script must return the output parameter @QUERY containing the query to be displayed in the Tree Page Tab.

Example

.VBSCRIPT
sub main()
	DBWInit(TRUE)
	uid = DBWInput("@DOCUMENT_UNIQUE_ID")
	if uid = 0 then
		exit sub
	end if
	length = DBWQueryByUId( uid, DBWLookUp("NAME_FIELD_LENGTH") )
	if length = 0 then
		exit sub
	end if
	lengthMax = length * 1.1
	lengthMin = length * 0.9
	query = _
		"SELECT "&_
			DBWLookUp("NAME_FIELD_T") & "," &_
			DBWLookUp("NAME_FIELD_ID") & "," &_
			DBWLookUp("NAME_FIELD_LENGTH") &_
			",*" &_
		"FROM " &_
			DBWLookUp("NAME_DOCUMENT_TABLE") &_
		" WHERE " &_
			DBWLookUp("NAME_FIELD_LENGTH") & ">=" & lengthMin &_
		" AND " &_
			DBWLookUp("NAME_FIELD_LENGTH") & "<=" & lengthMax &_
		";"
	' return the query to DBWorks
	DBWOutput "@QUERY",query,ForWriting
end sub

The RMB→Find a Document … functionality works now also on Projects kepts closed for performance issues.

DBWorks checks if the document to be searched is between the children of the selected project and expands it only when needed.

Enable drag-and-drop in Trees

Enable drag-and-drop on Assemblies

Only for fake components

The new sub-option allows the drag&drop of components into existing assemblies only if the components have been created with the Create New Bom Item functionality (fake components).

The options change the global User Interface style for the current user.

A new sub-folder named Styles, located under the SCHEMA\IMG folder, contains the available style files.

The style named MechWorksStyle.Default is the one used by DBWArm and other applications with no Users parameters.

The display of the Checked-out-by-others, Not-revision-managed, Standard-part attribute has been enhanced.

Generic Documents are now always displayed with the correct type icon independently of the above attributes state.

It is now possible to define some hot-keys through the definition file SCHEMA\DBWHOTKEYS.TXT, or, in it’s user specific version, USERS\<user name>\DBWHOTKEYS.USR.
Both files are managed by DBCustomizer.

;===================================================================
;
; DBWorks2007(C)MechWorks Hot-keys definition file
;
; Format:
;
; HOT-KEY-ID	<DBWShell command> | <@SpecialCommand>
;
; Where:
; HOT-KEY-ID	F1|F2|F3|...|F12|0|1|2|...|9|A|B|C|...|Z
;
; HOT-KEY-ID can be prefixed by CTRL- or SHIFT- for applying the hot-key
; only when the CTRL or SHIFT keys are pressed
;
; The allowed special commands are:
; @SEARCH	move the input focus in the [SEARCH] edit box
;
;===================================================================
CTRL-A		Checkout
SHIFT-A		Checkin
F5		Requery
CTRL-Q		@SEARCH
CTRL-B		ExecScript CalledFromHotKey.vbs

It has been removed the limitation on max 700 rows to be copied in the clipboard. The Ctrl+C can copy an entire large grid, and the result is available for pasting into MS Excel or any other Windows application.

• In the Document Selector dialog it is now possible to select the column’s headers of both the Prev.Rev. and the Script columns, and have all the rows be affected by the selection change:
• In the Multiple Checkin/Approve operations, any check-box activated in the Document Selector dialog is correctly restored after the check for not null fields ( with or without any consequent multiple editing for filling the null fields )

The following message boxes have been enhanced for supporting the “[X] Do not show this message again” check-box:

• multiple document selection
• current project
• add all documents to a project

DBWorks 2007 supports now multiple Visual Cues Definition files.
The purpose is to allow the user to display sets of Visual Cues, depending from specific conditions he likes to highlight.

The application looks in the SCHEMA\IMG directory for files with the naming convention: DBWVisualCuesDefinition_*.txt

The available file suffixes are listed in the Options→User Options tab:

allowing the user to select the desired Visual Cues definition file.

Once selected, DBWorks will reload the Visual Cues definitions, so dynamically changing the current Visual Cues visualization.

Example

The new position code 3 can be assigned to a Visual Cue, allowing the Visual Cue to be right-aligned. The <Tree Img Offset> and <Grid Img Offset> parameters must be negative.

Example

;--------------------------------------------------------------
; DBWVisualCuesDef.txt
;
; DBWorks Visual Cues Definition File
;
;--------------------------------------------------------------
; "<field name>","<field value pattern>","<Image Definition>",<Img width>,<Position Code>,<Tree Img Offset>,<Grid Img Offset>
;
; <Image definition>::=
;		a .BMP/.JPG/.TIF/.PCX/.TGA file name, or …
;		@Line,<pen width>,R,G,B
;		@Cross,<pen width>,R,G,B
;		@Rectangle,<pen width>,R,G,B
;		@Ellipse,<pen width>,R,G,B
;
; <Position Code>	0: full row; 1:icon; 2: text; 3: right-side full row
;
"T","A","dbwscbar149.bmp",18,3,-24,-24

The new parameter @SILENT (value [0/1]) is passed to the OnGetWorkflowProcess.LST

The parameter is 1 when DBWorks requests to return the process without any user interaction.

The following is an example of the script OnWorkflowStateHasChanged.LST, adapted for sending a notification e-mail to all the users that have the EMAIL field not null in the DBWORKS_USERS table.

 .VBSCRIPT

const temporaryZipAttachmentFileName = "C:\temp\attachment.zip"

sub main
	DBWInit(TRUE)

	silent = DBWInput("@SILENT")
	ecoId = DBWInput("@ECO_ID")
	process = DBWInput("@PROCESS")
	fromState = DBWInput("@FROM_STATE")
	toState = DBWInput("@TO_STATE")
	docUid = DBWInput("@DOCUMENT_UNIQUE_ID")
	allOk = DBWInput("@ALL_OK")

	DBWShell("WorkflowGetNotesAndFileAttachment " & docUid )
	notes = DBWResult("@WORKFLOW_NOTES")
	attachment = DBWResult("@WORKFLOW_ATTACHMENT")

	id = DBWQueryByUid( docUid, DBWLookUp("NAME_FIELD_ID") )
	user = DBWGetOption("USER_NAME")

	ReDim Preserve userList(1)
	DBWorkflowGetUserList toState,userList
	for j=0 to ubound(userList)-1 step 4
		userId		= userList(j)
		fullName	= userList(j+1)
		phone		= userList(j+2)
		email		= userList(j+3)

		nameToAddress = userId & "@" & DBWGetOption("COMPANY_ID")

		if DBWGetOption("DBWARM_USER") <> userId then
			sendNotificationEmail nameToAddress,id,fromState,toState,user,attachment
		end if
	next

end sub

sub sendNotificationEmail( nameToAddress, id, fromState, toState, user, attachment )
	SUBJECT		= "Workflow notification: " & id & " - state changed to """ & toState & """"
	BODY_HTML01		= "<html><body>"
	BODY_HTML02		= "<h1 align=""center""><FONT face=""Verdana"" size=""5"">DBWorks Workflow Notification</FONT></h1>"
	BODY_HTML03		= "</br>"
	BODY_HTML04		= "Document"
	BODY_HTML05		= "<h0 align=""center""><FONT face=""Arial black"" size=""3"">" & id & "</FONT></h0>"
	BODY_HTML06		= "</br>"
	BODY_HTML07		= "has changed state from"
	BODY_HTML08		= "<h0 align=""center""><FONT face=""Arial black"" size=""3"">" & fromState & "</FONT></h0>"
	BODY_HTML09		= "to"
	BODY_HTML10		= "<h0 align=""center""><FONT face=""Arial black"" size=""3"">" & toState & "</FONT></h0>"
	BODY_HTML11		= "</br>"
	BODY_HTML12		= "</br>"
	BODY_HTML13		= "Sent by " & user & ", " & Date() & "</br>"
	BODY_HTML14		= "</br>"
	BODY_HTML15		= "</body></html>"
	if attachment<>"" then
		DBWShell("FileZip New " & replace(temporaryZipAttachmentFileName," ","|"))
		DBWShell("FileZip Add " & replace(attachment," ","|"))
		DBWShell("FileZip Create")
		ATTACHMENT01 = temporaryZipAttachmentFileName
	end if

	DBWShell("EMail New Notification "		& nameToAddress )
	DBWShell("EMail Data SUBJECT "		& replace(SUBJECT," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML01," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML02," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML03," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML04," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML05," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML06," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML07," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML08," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML09," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML10," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML11," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML12," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML13," ","|"))
	DBWShell("EMail Data BODY_HTML "		& replace(BODY_HTML14," ","|"))
	DBWShell("EMail Data ATTACHMENT "		& replace(ATTACHMENT01," ","|"))
	DBWShell("SendEMail")

end sub

DBWorks ADW 2007 introduces a support for duplicating a snapshot of the current status of an assembly. The assembly file names are generated with a time stamp and current revision info. The assembly snapshot can be registered in the database or attached to the original document with the new DBW_ATTACHMENTS managed by DBWorks.

A new page in the options defines the settings for the As-Built duplication.

When registering As-Built assemblys they will be located in the As_Built project (auto-created) under a sub-project named as the sub-assembly.

When registering As-Built assemblys as attachments they will be located in Attachments tab.

The custom query will now define the documents that MUST be converted.

A new option for defining the load on different workstations has been added .

When the option is set the Conversion Wizard will create a file with the a number of queries to be loaded on, as custom query ,on each workstation. The file will be opened in notepad after confirming the Conversion Wizard dialog.

This Wizard allows to import documents, properties and revisions from an existing PDMWorks for Worgroup installation.

The tool requires DBWorks StandAlone 2007 and a SolidWorks 2007 or better.

When you start the Wizard, you need to log into PDMWorks from within the wizard.

Then you must select the projects to import. If you have a large number of documents importing the projects in separate batches can be a good idea.

After selecting the project you are presented with the list of properties and configurations. Here you must select the properties you want to import and associate them with the fields of the DBWorks records. If needed you can create new fields to store the information coming from the custom properties of the files.

If you import the configurations (DBWorks will treat each configuration as a separate record) you can select a set of configurations to import or to ignore.

In the final tab you start the migration.

During the migration the files are first extracted to a selected path and grouped in sub folders, then registered one by one.

It is possibe to use both SolidWorks or DBWorks Stand Alone to register the files, but DBWorks Stand Alone is generally faster.

• Support for sort order of browser tables in DBCustomizer 5.2.5
• More info in the updates suggested: type and size of field to be added indicated explicitly
• Support for Linked Tables

  Linked Tables can be managed from DBCustomizer selecting the entry Customize, Linked Tables

  The interface allows you to specify that a field in the DOCUMENT table is used as a key to link an external table as an extension of the DOCUMENT table:
  

  How to add a link:

  1. click the button just below the header
  2. select the table
  3. select the field inside the table
  4. select the linked field in the DOCUMENT table

  Automatic behaviors in the interface to simplify the task:

  • When you select a different table the list of fields on the right is filled automatically, the Primary Key, if available is selected. If the primary key includes more fields, the first is selected.
  • When you select a different field in the external table if the field is of type test the field ID is selected automatically as the foreign key in the DOCUMENT table; if, on the other hand the field is numeric the field UNIQUE_ID is selected as the foreign key in the DOCUMENT table.
  • You can change the selection for the DOCUMENT field used as the foreign key manually.

• Support for Custom Fields in every table. Support for the protection of basic fields in REVISIONS and PARENT_CHILD.
• Adding a field with the name of an existing text one and with different size changes the field size in the database
• In the Manager for the Shortcut Bar it is now possible to set icons up to an index of 250 (previously it was 150). The naming convention and file location of the bitmaps is left unchanged.

• Support for open/save as with filter on files, icons added to the toolbar
• DBWJComp.dll includes the old VisualCuesManager.dll, now obsolete
• Support for SQL conditions on any database table

• Added ability to filter out models that have a drawing
  • The interface in the designer has slightly changed, passing from a check to a list
    
    
  • The parameter that can be added to the files PAR\DBWBOM_* is FILTER_OUT_DOCS_WITH_DRAWING
• The Excel BOM Designer controls the validity of the field names for the DOCUMENT table
• Added new option to exclude Generic Documents from the BOM, made independent from part-part relations management
• Reordering is now managed in case of first level duplicates for BOMs of projects
• Options first residing in the DATAENTR>LST have been exposed in the Options dialog of Category Maker
• Excel BOM supports the Linked Tables
• Support for the display of only one item when there are several parents
• Support for custom PARENT_CHILD fields. The fields are available in the EXCEL BOM Designer for the BOM items but not in the header.
• Support for REVISIONS in the BOM engine contained in the object MWScriptGui.BOM .

  The scripts in the ExcelBOM.lib library had to be updated to include the new function
  ExcelBOMRevision(uid, revision)

  Another function has been added to avoid lack of generality:
  Function ExcelBOM3(uid, par_file, excel_file_name,revision)
  where the last parameter should be an empty string for the current revision and the revision for which the BOM is requested otherwise.

  Also the function BOMRecordset in the object MWSCriptGui.BOM now has an added optional parameter for the revision name and it returns a recordset with the current BOM if the revision is a null string and the BOM for the requested revision otherwise. All changes are backwards compatible. Note that for previous revisions you cannot obtain information about the parents of the items, namely projects and drawings because such information would not be accurate.

• Behavior change: eliminated the restriction that would keep categories from indicating a sub-path instead of a simple category name
• In Save Wizard missing metacategories are created on the fly instead of displaying an error message
• Support for ‘.’ As a sub-codes separator
• The label of the button to close the application has been changed to ‘Exit’ for the sake of clarity

• Clicking other documents in the same ECO updates the preview panel

• Eliminated duplicate entries in the values displayed for date fields. Equals still doesn’t apply to date/time fields as they are expressed in milliseconds.
• The parameter file SCHEMA\AdvFilterFields.txt controls the list of fields that appear in the leftmost combo box of custom conditions in the Advanced Filter. The parameter file is a simple list of the fields with the same name that they have in the DOCUMENT table of the database. The parameter file must contain at least one valid field name. The entry ‘anywhere’ remains always visible. A valid example of file content is the following:

  ID
  FILE_NAME
  FILE_DIRECTORY
  DESCRIPTION

  The usual editing rules for comments apply to this parameter file; there currently is no GUI editing tool for this file.

A new version of WebClient will be released shortly after the release of DBWorks/DBInventor 2007

• The dialog box, displayed when detaching DBWorks as an add-in of SW, asking for the reset of the original SW settings, is no more displayed, being managed automatically
• If the Save Wizard is active (Options Open/Save→Save As→Use Dataentr.LST ), when working with the configurations activated, for weldment parts, if the active configuration is the <As Welded>, DBWorks activates the parent <As Machined> configuration, for avoiding rename conflicts (generating SW errors) when the derived <As Welded> configuration is renamed before the <As Machined>

1. The functionality expects a selection; it no more works on the whole grid result set
2. The functionality works also from the Tree Page
3. The functionality creates a temporary user table named DBW_LOCKED_FILES_<user name>; the global DBW_LOCKED_FILES table is no more used
4. The DBW_LOCKED_FILES_<user name> table has the following structure:

   T			VARCHAR(1)
   ID			VARCHAR(256)
   USERID			VARCHAR(256)
   SERVER			VARCHAR(256)
   DESCRIPTION		VARCHAR(512)
   FILE_DIRECTORY		VARCHAR(256)
   FILE_NAME		VARCHAR(256)
   STATE			VARCHAR(40)
   CONFIGURATION		VARCHAR(256)
   REVISION		VARCHAR(40)
   COMPANY_ID		VARCHAR(256)
   OWNER_COMPANY_ID	VARCHAR(256)
   CHECK_OUT_BY		VARCHAR(256)
   UNIQUE_ID		INTEGER

The BIN\DWGView.EXE is obsolete and it has been removed;
consequently, the RMB→Preview of …DWG functionality, uses now the new DWG viewer

Even if the option Open→Don't open related documents on checkout is unchecked, any linked Generic Document is no more automatically opened by DBWorks