• Share
    • Twitter
    • LinkedIn
    • Facebook
    • Email
  • Feedback
  • Edit
Show / Hide Table of Contents

traveller Table (31)

Some tooltip text!
• 3 minutes to read
 • 3 minutes to read

Associates traveling out from this database

Fields

Name Description Type Null
traveller_id Primary key PK
systemlevel level in hierarchy UShort ●
travel_id Central=0, Departm.=H01000000-H7F000000, Travel=assoc_id FK associate ●
area_id ID of Area this traveller is on Id ●
generatedtime Time of exit (local update) DateTime ●
last_recordtime Datestamp from last traveltrans record read from this traveller (async) DateTime ●
last_recordnumber Record ID of last traveltranslog record receieved from this traveller FK traveltransactionlog ●
last_playbacktime Datetime when we last read a file from this traveller DateTime ●
last_playbacknumber File number of last file receieved from this traveller FK traveltransactionlog ●
databasetype The database type he has UShort ●
encryptedComm Use encrypted communication for this traveller: 0 = no, 1 = serial no as key, 2 = target db tag as key (secure but lots of hassle for support) Enum TravelEncryptionChild ●
dbTag Database tag, used for encryption key String(39) ●
defaultMakeReturn Default value for the 'make return log' checkbox, based on last answer UShort ●
registered Registered when UtcDateTime
registered_associate_id Registered by whom FK associate
updated Last updated when UtcDateTime
updated_associate_id Last updated by whom FK associate
updatedCount Number of updates made to this record UShort

traveller table relationship diagram

Database type

Databasetype ID Comment
Sybase Anywhere 1 requires owned license from Sybase Anywhere.
C-tree 2 OBSOLETE!
MSDE 3 Microsoft MSDE (Microsoft Desktop Engine)
BuildIn 4 Replaced c-tree (v.6), actually Sybase which is locked to the SuperOffice application.
SQL Express 5 Microsoft SQL Express 2005-
encryptedComm ID Comment
None 0 Transmitted travel data are not encrypted (only ZIPed)
Serial 1 Transmitted travel data are encrypted using licence serial number as key
BF128 2 Transmitted travel data are encrypted using a 128-bit key

Indexes

Fields Types Description
traveller_id PK Clustered, Unique

Relationships

Table Description
activeuser Currently logged-on users. This table contains encrypted license information. Changing it may disable login for all users and require intervention by SuperOffice support. Recommended use: for determining who is logged on, at what location, etc.
associate Employees, resources and other users - except for External persons
traveltransactionlog Log of all updates made to the database, that need to be replicated.

Replication Flags

  • None

Security Flags

  • No access control via user's Role.
In This Article
© SuperOffice. All rights reserved.
SuperOffice |  Community |  Release Notes |  Privacy |  Site feedback |  Search Docs |  About Docs |  Contribute |  Back to top