1. When using the DBAccess agent to write to an Access database, I was unable to update or delete data from this database, while the Adroit Agent Server was running, all I was able to do was read its data - how can I prevent Adroit from locking the Access database?

Answer:
Install Microsoft JET 4 SP 7 and the latest MDAC 2.7 release 1, on the Adroit machine Note: You need to install the Microsoft JET 4 SP 7 that is specific for your operating system, e.g. if you are running Windows 2000, you need to get the SP 7 for 2000. All the drivers are available from the following Microsoft web site: http://msdn.microsoft.com/library/default.asp?url=/downloads/list/dataaccess.asp

2. Can one input values from Excel to Adroit mimics?

Answer:
Yes. Use the Production Report Utility (PRODREP97.XLS) found in the Samples folder, which provides a sample of what can be achieved using the OLE interface. For more information, search for this Adroit Help topic: Management Information Reporter

3. How do you send messages via e-mail with the Notify agent?

Answer:
Although the Adroit help file may mention ‘e-mail’ as an option for Notify agents, we recommend that you use our sample ‘send_mail.bas’ script to send e-mails instead. This script can be located in the ‘Samples\Scripts’ folder off your Adroit system folder, which is typically ‘C:\Adroit’.

4. How can I log alarms and events to an Access database by using the EventOutput agent?

Answer:
When configuring the EventOutput agent (as outlined in the Adroit help topic entitled “To Configure an EventOutput Agent to Log to an Access Database”), ensure that the following steps are performed:
1) Enable Size Printing (select Yes) and type a 1 in the Size drop-down list box, so that Size = 1, otherwise you will have to wait until Page is Full or File is Full before the agent logs the contents to the database.
2) Under Format, ensure that the columns correspond with the fields in the database. (It is recommended to add the columns one by one).

5. Is there an Excel Add-In in Lotus?

Answer:
No, although OLE to Lotus may work, but we suggest the use of DDE or Excel as we are not familiar with Lotus OLE.

6. How can I use only the MISSRVR without installing the entire Adroit application?

Answer:
If installing Adroit 5, choose the Custom installation option and select the OLE Interface Only to do this. Otherwise, choose one of the following methods: Method A: Map a network drive to a computer with Adroit already on it, and just run the MISSRVR program once. This will require a permanent reliable network connection to the Adroit computer, and also means that if that computer software gets upgraded, the "Client" must close so as not to lock any files. Method B: Copy the following files from an existing Adroit installation directory: afcdll.dll; aspublic.dll; elclnts.dll; iafc.dll; missrvr.exe and pool.dll. Run MISSRVR program once to register it. so as not to lock any files. This avoids the problems associated with Method A, but may cause version problems if these copied files are not upgraded when the existing Adroit installation is upgraded. The client computer will also require the MFC60 DLL files.

7. Can Access and Excel be used together on one PC with OLE?

Answer:
Yes, however you must remember that each program that uses OLE (i.e. the Adroit MIS server) uses one connection each.

8. Can I filter events before they are printed?

Answer:
No - the event printing mechanism is designed to be a total event dump for post analysis. If you require post filtering, use the FILE or SQL options of the event output agent. This routes the events to a file or database that will allow post filtering and printing with 3rd party tools.

9. Why will the Excel Add-in function not initialize?

Answer:
OLE takes up one license connection point, check that there is a license point for this view node. For more information, search for this Adroit Help topic: Management Information Reporter

10. Why do I get a Queue lock timeout message box when starting a data log?

Answer:
One of the reasons for a queue lock timeout is caused by trying to log values to a SQL database on a PC that has run out of hard disk space. Unfortunately the OLE DB mechanisms provide no way of interrogating the host PC about it's state, especially the amount of space that remaining on the hard drive. All datalogging and DBAccess interaction with external databases require some level of external manual or automatic maintenance to ensure that they do not run out of resources. For instance backups and / or deleting obsolete or stale records of these databases. SQL Server also has the capability of configuring jobs that can be scheduled as and when required for the same purpose. For instance, jobs can be configured for deleting stale records.