Re: [Emerald] BIG PROBLEM

Richard Sensale ( (no email) )
Mon, 3 Jan 2000 12:26:12 -0500

Um, it is happening with every record.. Additional info. Looks like it is
only happening on some of our client machines. If I go in on one of my
other machines it works fine. But on three of our machines, the red flag
still shows up. It seems to be updating the database though... Maybe a
client issue or something. Does the client inteact with the system clock.
Im not 100% sure that the bios in those machines are 100% Y2K compatable.
-----Original Message-----
From: Dale E. Reed Jr. <>
To: <>
Date: Monday, January 03, 2000 12:14 PM
Subject: Re: [Emerald] BIG PROBLEM

>Brad Facer wrote:
>> are you adding the extension to the masteraccount or the indiv.
>> we've run across this before where the MA extension was 0, the SA
>> was 5, and the MA took precendence, causing a 0 extension.
>Actually, the MA extension extens the MasterAccounts ExpireDate, and
>the SA extension extends the SubAccounts expireDate. If the SA
>ExpireDate is NOT NULL, then it will take precedence over the MA
>ExpireDate. In no situation is the MA extension used on the SA
>ExpireDate or vice versa.
>We have ran into situatoins where people put in an sa ExpireDate, which
>will cause the above problem, since the MA expiredate/extension is
>not used. In the latest Emerald, you can enable viewing of the
>sa ExpireDate in the admin. I do *NOT* recommend this, as you should
>not be using the sa ExpireDate fields at all.
>Dale E. Reed Jr. Emerald and RadiusNT
>IEA Software, Inc.
>For more information about this list (including removal) go to:

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