udsalelarge Table (159)

User-defined fields

Fields

NameDescriptionTypeNull
udsalelarge_idPrimary keyPK
string41string value 41, indexedString(199)
string42string value 42, indexedString(199)
string43string value 43, indexedString(199)
string44string value 44, indexedString(199)
string45string value 45, not indexedString(199)
string46string value 46, not indexedString(199)
string47string value 47, not indexedString(199)
string48string value 48, not indexedString(199)
string49string value 49, not indexedString(199)

udsalelarge table relationship diagram

Indexes

FieldsTypesDescription
udsalelarge_idPKClustered, Unique
string41String(199)Index
string42String(199)Index
string43String(199)Index
string44String(199)Index

Relationships

TableDescription
saleSales For every Sale record edited through the SuperOffice GUI, a copy of the current version of the record will be saved in the SaleHist table. This also applies to editing done through the SaleModel COM interface, but not to editing done through the OLE DB Provider or other channels.
SaleHistMirror image of the Sale table, providing a full transaction history. Every time you edit a sale, the current record of the sale is also saved here.

Replication Flags

  • Area Management controlled table. Contents replicated to satellites and traveller databases.
  • Replicate changes UP from satellites and travellers back to central.
  • Copy to satellite and travel prototypes.

Security Flags

  • Sentry controls access to items in this table using user’s Role and data rights matrix on the table’s parent.