7.4

Pidget
Type of PlanetPress Capture object. Page element used to give instructions to the Anoto pen, as opposed to recording ink.
PlanetPress Capture Database
A database containing the list of patterns, sequences, registered pens and documents. The Capture Database can be used by a
single server, or by multiple servers in a Client/Server architecture.
Session
The time spent by the pen between events that trigger a new session. Generally a session refers to any ink in a single page
containing a Capture Pattern. Asession can contain ink from multiple fields in any order. A new session starts whenever a
PGCis sent for processing (which erases the data from the pen).
General Considerations
Here are some general considerations in regards to PlanetPress Capture, its environment, the hardware and the software that
interacts with it. Please review these considerations carefully as they may impact PlanetPress Capture and its functionality.
PlanetPress Capture Fields cannot simply be inserted into an existing document as-is and expected to work properly,
efficiently or consistently. In order to design a document with Capture Fields, you must review and understand the
Critical PlanetPress Capture Implementation Restrictions.
Database Considerations (ODBC)
On 64-bit operating systems, the ODBCData Sources created by the Data Source (ODBC)icon in the Administrative
Tools will not appear here, as PlanetPress Suite is 32-bit and cannot access the 64-bit data sources. In order to create
an ODBCconnection visible by PlanetPress, you will need to access the 32-bit version of the ODBCmanager, avail-
able in C:\Windows\SysWOW64\odbcad32.exe .
The following considerations should be kept in mind while working with ODBCDatabases in PlanetPress Suite.
l All databases
l User Rights:During normal operation, Read/Write to tables should be sufficient. However, during the initial
setup, the Create/Drop tables rights is necessary.
l Minimum 100MBof database size is required as a minimum, but the space requirement is dependant on the
implementation. The more active documents in the database, the more space is used - note that this pro-
gression is rather linear.
l Regular database maintenance is required, such as database compacting, is required by a system admin-
istrator.
l It is recommended to create an ITprocess that backs up the database regularly.
l The recommended ideal setup is a dedicated SQLServer PC, accessed by PlanetPress Workflow through an
ODBCconnection on the local network.
l Microsoft Access
l Database file (mdb)must be local to the PlanetPress Workflow computer. It cannot be located on a network
drive or another server.
l Total database size is limited to 4GBof data.
l Total size of a single table is 2GB.
l May be unstable in large implementations.
Special Workflow Types