Requirements for the Change locations procedure

The Change locations procedure in your Adlib Museum application allows you to simultaneously change the current location of one or more marked object records in the Brief display, when you are actually moving objects.
The Change locations procedure (in Adlib for Windows 7.1 and higher, not Axiell Collections) uses hard coded tags for its field mapping. If you want to customize an application, it might be handy to have an overview of the relevant tags. To start with, Adlib distinguishes between 4.2 model applications and older model applications. This distinction is made on the basis of tag 2A (current_location) in the database collect. If the tag is present, the software assumes that it concerns application version 4.2 or higher. So, this tag in that database should not have a different purpose, in whatever application, if you want to be able to use the Change locations procedure.

For application version 4.2 and higher, the following applies:

Field in Change object locations window

Tags to be filled by the procedure in database collect

Location

2A (Current location)

Date/Time

2C/2G, the start date and time of the new current location (and SE/Sh, the end date and time of the now previous location, if present)

Suitability

2E

Authoriser

2F

Notes

2D

Method

mT (Movement method)

Reference

mR

Contact

mC

Notes

mN

 

2R (current executor)

When the procedure automatically transfers the details of the current location to a new first field group occurrence of the location history (which of course happens before the procedure enters a new current location), the following tag mapping is used in 4.2.

Current location fields

Location history fields

2A (Current Location)

ST

2C/2G (Date/Time)

SS/SH

2E (Suitability)

S3

2F (Authoriser)

SP

2D (Notes)

LM

2R (current executor)

2V (executor history)

In the 4.2 model application, 2R and 2V have not been defined in the database structure yet and are not visible on the screen (they will be in a future model application), but they will still be stored in the record. In principle that is not problem. If you want, you can define 2R and 2V as text fields with a length of maximally 100 characters in the collect database (2R not repeatable, 2V repeatable) and place them each on their applicable location screen, right above the Authoriser field for example, to make this data visible.

For application version 3.4 and older applies:

Field in Change object locations window

Tags to be filled by the procedure in database collect

Location

ST

Location type

LT

Date

SS, the start date of the new current location (and SE(2), the end date of the now previous location, if present)

Notes

LM

Before the procedure enters a new current location, a new, empty first occurrence of the field group for the location details is created. This means that the data from the old first occurrence simply moves down to the second occurrence, which makes the old current location the new previous location. The relevant tags in 3.4 are the following:

Current location fields

Location history fields

ST(1) (Location)

ST(2)

LT(1) (Location type)

LT(2)

SS(1) (Start date)

SS(2)

LM(1) (Notes)

LM(2)

S3(1) (Suitability)

S3(2)