Specifications

98 Using Databases with ID Works Projects
ID Works Standard and Enterprise Version 5 Administrator’s Guide
ID Works fields of type Auto Sequence map to:
To prevent duplicate values, the column connected to the auto
sequence field should be restricted to unique values using an index or
constraint.
Controlling Database Activities
Depending on the type of database used, there are two or three
levels of database access control in an ID Works project. The
database administrator is the only person who can grant privileges,
and granting privileges happens outside of the ID Works program.
For some databases, you can further restrict access (but not extend
access) when you select the data source.
The best place to restrict Production operators’ database access is
on the Database tab of the Edit Production Form Properties dialog
box. There you can prevent operators from creating new database
records, saving changes to records, deleting records, or searching
the database. Note that when you use the Database tab of the Edit
Production Form Properties dialog box to restrict database access,
those restrictions are applied to all ID Works users of the project,
regardless of the user privileges individual user accounts were
granted when the accounts were set up. The print count field
overrides settings on the Database tab of the Edit Production Form
Properties dialog. That is, if Save is cleared on the Database tab of
the Edit Production Form Properties dialog and a Production operator
prints a card, the database record will still be updated to increment
the database table column associated with the print count field.
You can restrict individual users’ database access through the
Manage User Accounts utility in the ID Works Administrator
application. Each user’s privilege to search, add or change records,
Access data types Number(Integer), Number(Long
Integer)
DB2 data types Integer, Smallint
Oracle data type Number(x,0)
SQL Server data types Integer, Smallint