$ALARM data members

[Carl Finley]

I am having trouble with my $ALARM data members. I am trying to utilize these for some functions, however, there are bogus values in these fields. I am specifically referring to the 'unacked' data member. I have 6 active alarms which have all been acknowledged. The value in the $ALARM.Lookout.unacked field is 25. The value in the root $ALARM.unacked field is 44. The value in the $ALARM.Priority01.unacked-Priority10.unacked is 0 (even with active unacknowledged alarms). Can any one tell me where these numbers may be coming from? Thank You.

[Carl Finley]

Never mind, I found out that these were from other processes that had been developed on the same PC. Alarms that were not acknowledged prior to closing were logged in the database. All processes were using the default location for the database and therefore were all using the same folder. By deleting the folder it cleared all old data and automatically regenerated a new folder.

[Loren]

During development I get bogus Alarm information. I typically just delete
the ..../database/areas.dat file. You are saying the entire database
directory can be deleted without harm to the Lookout program?

"Carl Finley" wrote in message
news:50650000000500000000250000-986697009000@quiq.com...
> Never mind, I found out that these were from other processes that had
> been developed on the same PC. Alarms that were not acknowledged prior
> to closing were logged in the database. All processes were using the
> default location for the database and therefore were all using the
> same folder. By deleting the folder it cleared all old data and
> automatically regenerated a new folder.

[Carl Finley]

Yes, you can delete the lookout/database folder. You will lose all stored data also, but in the development stage that doesn't bother me. Lookout will automatically regenerate the folder. It would probably be better to do it as you said though.