RE: [Emerald] Expiration "slipping"

David V. Brenner ( (no email) )
Mon, 23 Aug 1999 16:28:47 -0700

> > Even more bizarre, a user whose billed thru and expiration dates were
> > 8/31/99 and 9/1/99, respectively, at 11:00 this morning are now
> expired and
> > both fields are set to 5/5/99.
> What does the LastModifyDate/User fields show for the account? Does
> 5/5/99 mean anything on the account (like when it started, etc)?
> What automated tasks you do have running at night?

5/5/99 is the creation date. We have one user service (PPP) defined that
was last modified on 5/27.

When my billing person noticed that the expiration and billed thru dates
were set to 5/5, it was about 2:00 p.m. and the Master tab showed that the
record had been modified at 11:00 a.m. today. She insists that she did not
save the record at that time, but admits to looking at it. Even if she had
saved the record, it is doubtful that she would have typed in those dates,
especially since we bill monthly and always set expiration dates to the
first of the month.

As for nightly processes. I do a complete dump of the Emerald device at
4:00 a.m. About once a week, I switch to a new backup and delete the old
set. I also have a process running that resets the Time Left field each
month. This is a routine that you posted to the list a while back. 99% of
our accounts are not affected by the script as the Time Left field is null
for everyone but a handful of senior citizens who buy 60 hours per month.

Frankly, if it wasn't for the presence of that particular date in that
record, I would think she was making some kind of mistake, but that date is
just way out of whack.

David V. Brenner -
International Services Network Corporation

For more information about this list (including removal) go to: