udsalelarge Table (159)
Some tooltip text!
• 2 minutes to read
• 2 minutes to read
User-defined fields
Fields
| Name | Description | Type | Null |
|---|---|---|---|
| udsalelarge_id | Primary key | PK | |
| string41 | string value 41, indexed | String(199) | ● |
| string42 | string value 42, indexed | String(199) | ● |
| string43 | string value 43, indexed | String(199) | ● |
| string44 | string value 44, indexed | String(199) | ● |
| string45 | string value 45, not indexed | String(199) | ● |
| string46 | string value 46, not indexed | String(199) | ● |
| string47 | string value 47, not indexed | String(199) | ● |
| string48 | string value 48, not indexed | String(199) | ● |
| string49 | string value 49, not indexed | String(199) | ● |
Indexes
| Fields | Types | Description |
|---|---|---|
| udsalelarge_id | PK | Clustered, Unique |
| string41 | String(199) | Index |
| string42 | String(199) | Index |
| string43 | String(199) | Index |
| string44 | String(199) | Index |
Relationships
| Table | Description |
|---|---|
| sale | Sales 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. |
| SaleHist | Mirror 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.