AMS – ODBC Driver

ODBC drivers are the interface used between the program data files and the Windows printer function.  We have noticed that several 3rd party software programs may overwrite the ODBC settings used by AMS32 in report printing.  These include MS Office, xx & MS Intellimous installations.    This is evidenced by an error box indicating an ‘ODBC’ error.  ODBC driver errors can be rectified by running the ODBCInstall.exe file from the ‘SETAMO’ directory or the original CD

Using the Item Trigger feature in Status

There are a number of situations where one item is only due after the compliance of another item.  This option is now available in the schedules where a trigger value can be entered in the item beeing triggered.  Together with this feature, we have implemented an option to make items non repeat items.

The configuration of these links can be done from the Status program on Window W1500.

 

Implementation of SharedID

As we have implemented the possibility to move schedules from one data base to another, we can not assume that the ItemID field will be unique once a schedule has been move to another database.  For this reason, we have implemented a SharedID field.  It is important to keep in mind that only one server can allocate SharedID numbers and this must be the parent server.  In a user environment where a server is the only server and there is no expectation to import schedules at a later stage, the server is by default the parent server.  Users can allocate their own SharedID values for each item in a schedule. This can be done from the Schedule Window W1300.  Once SharedID fields are allocated, they will be visible on reports as well as on W1500 where schedules are edited.  Each item in a schedule has a unique ItemID followed by a Shared ID which is unique amongst all servers sharing the same Schedule.  Note the value in brackets, which is the the sharedid allocated, next to the ItemID which is unique to your database.

 

Repeat Items

Users will notice that the latest Status program makes provision for a “Repeat status” on an item.  The default is for all items to be repeat items as that is the way schedules were designed in the past.  There is however situations where an item is due within a specific period and the becomes inactive.  This was previously handled by the “Single” item type, but had the disadvantage that these items always showed with a Due status.

By marking an item as a non-repeat item, the status of the item will change to inactive once it has been complied with and an Install date was given to the item.

Trigger Items

The trigger requirement followed on the repeat item feature.  This is used where an item is activated once a previous or parent item has been complied with.  It is important that the parent item is of the type Non-repeat and must have a SharedID allocated as described above.  Simply move to the child or triggered item and enter the SharedID of the parent item in the trigger field.  You can then select the Trigger button next to the field that will check the validity of the value entered.

 

Calculation

It is important for users to understand how the calculations are done and the status of these fields are activated.  Most of the calculations are based on the presence of an Install Date.  To maintain integrity, this feature can only work automatically in one direction.  Providing am Install date will trigger the child field, but removing an Install date will not always undo the child activity as this might be incorrect.

Non-Repeat Items will automatically become inactive, once an Install date has been entered in the maintenance part of the item (W1600).  If an Install date is removed, no change will be made to the “Active” status of the item as users might want the item to remain inactive. 

A similar pricipal is followed when a child item is triggered by a parent item.  Once the Install date is supplied to the parent item, the triggered item will be made active and the parent compliance data will be carried over to the child or triggered item.  The child will therefore have the same install date, hours, cycles and landings of the parent item.  The information will depend on the type of parent item.  The exeption to this is in the event where the child was already active with  maintenance data at a later date, in which case no change will be made to the child or triggered record.

As before, this will not reverse automatically if the install date is removed from the parent item.  The reason is that there might be valid maintenance information recorded in the child item.  The child item will remain active with the data as recorded before.  Users wil manually have to remove this information from the child or triggered item if it was incorrectly allocated.

When the maintenance is calculated all triggered items without Installation dates will automatically be made inactive.

Index key file IDK

AMS uses a dBase file system.  The speed of this system depends on the accurate index files.  The default index file system used in AMS are CDX files due to their robust nature and flexible application capabilities.  The dBase system is fairly robust and faster than most other flat file systems.  The nature of the implementation of the shared client server processing makes the file system subject to corruption when power failures or network interruptions are experienced during operation.

AMS has been designed with an additional safety element.  This system simply keeps the last record ID in a Ascii file with an IDK extension.  When new records are added the new ID’s are checked against the ID stored in the Ascii file.  This simple method provides additional safety as it is immediately clear when an index file is potentially corrupt.

IDK files are created from the normal data re-index window.  Simply check the “Use IDK Reference” on the re-index window.  This will create the IDK files during re-indexing.  This will be the default as long as IDK files are found in the data directory.  Un-tick this check box to delete all the IDK files during the next re-indexing and the program will operate without this feature.

The IDK file system is an additional check that could assist with early detection of corrupt indexes and will in no way change the operation of the program.  These files can therefore be deleted at any time and it is not required to back them up as they can be generated during indexing.

T&T0003R1 Upgrading AMS executable and reports

The latest AMS program upgrade will from now on be on our ftp site for all users to download.  Downloads will be available through the AMS program.  For users on older version of the program the first upgrade can be done manually as described below, but this option will not be available in the future.
This upgrade includes various changes and fixes made over the past few months as well as report changes, which can be automatically downloaded directly from the ftp site from within the program.
There are currently two options for upgrading available to users.
1     Auto Upgrade:For those users with version 2.22.00 or later, open 'Housekeeping - Config Options - Company' and select 'Download Update'.  A download window will open and the program will automatically download the latest upgrade file from the ftp site. 
This download window can be closed when complete or will auto close five seconds after completion.  Later versions will offer to auto start the 'Setup.exe'.
If the program does not try to auto start the upgrade, exit and manually run Q:\Data\Setams\Setup.exe (where ‘Q’ is the default drive used for AMS installations.  This might differ on some sites).
To upgrade the report templates, open 'Housekeeping - Config Options - Company' and select 'Download Reports'.  A download window will open and the program will automatically download the latest upgrade file from the ftp site.  This download window can be closed when complete or will auto close five seconds after completion. Manually run Q:\Data\Setams\SetupReports.exe

2  Manual Upgrade
For users on progran versions prior to v2.22.00 use the ftp site to bring the program up to date.  This method of updating will be obsolute once all users upgraded to the latest version.
Download Site:
ftp://ftp.avdex.co.za    AMS
The ftp username is avdexftp and the password is avdata
Download the ‘Setup.exe’ file to the Q:\Data\Setams folder.  Run the ‘Setup.Exe’ on the first PC and follow the install instructions.  It is important to save the installation file in this directory where all users can access the installation file.
Please remember to close AMS32 on your PC when running the setup.  An error message most likely means that AMS32 is still open and cannot be over written.
Users not familiar with FTP sites could download from our online download site: Click Here and download the AMS installation file SetAMS.exe
3 Implementation
When the first user upgrades, ask all users to exit AMS.  Relaunch AMS. If the file structures need updating, the program will display a warning.  Select 'File Structure' and select each file that is not OK and press ‘Update’.  When complete, Exit re launch AMS and select ‘Housekeeping - System - Data Files - Build Index’ and press ‘Start Indexing’.

Once the first user has upgraded, the other users will be prompted to upgrade automatically when they next logon.

Reports
Download and save the file ‘SetupReports.exe’ and unzip to the ‘Q:\Data\Setams’ folder.

T&T0014R1 - Mapped Drives for AMS

AMS32 and Status make use of 'Mapped Drives' when connecting to data and other folders.  This is due to a number of reasons, not the least being a quirk in a report writer that does not see UNC drives.  As a universal setup, AvData have used the drive letter 'Q' to denote the data directory for AMS and 'P' for WinStatus.  (The new SQL version of Status does not require this definition)  This aids trouble shooting in telephonic support as all AvData drives are 'Q' or 'P'.

When setting up a new PC on a network it is essential that the drive mapping be in place prior to first launching AMS or Status.  When selecting the remote folder to 'Map', select the folder containing the 'Data' folder.  ie the one above the data in the tree as shown by Windows.  Both the report writers and the data files need to see a folder in the data drive.  This means that the data drive cannot be 'Q' but must be 'Q:\Data'.  As most installations on servers are done via a full installation, it is then easy to 'Map' the 'AMO' folder on the server as 'Q'. 

Cleints making use of the 'Multi Data' facility must always have the same folders mapped in an identical manner as these paths are stored in a file on the server and will produce warnings if the program sees different paths to the 'Multi Data' folders.

The data path for AMS will therefore aleways be 'Q:\Data'

Preferred method

1. Click the Start button
2. Right Click on My Computer
3. Select Map Network drive…
4. Enter the Drive (Q:)
5. Browse and select the network folder
6. Check Reconnect at logon
7. Select Finish

The exact format of the window might differ between operatings systems.

Visit the AMS web site