This is how the time banking does work. Time banking is NOT recurring,
though. So when either their account expires OR they run out of time, they
can not login. If the user runs out of time, their account doesn't really
expire, they just can't use it.
> Rather than keeping track of which accounts have been used and should then
> be expired (ie the subaccount deleted) after thirty days, we're hoping
> there's a way to implement something as listed above within Emerald or
> maybe by running an external SQL statement\Report every so often (hmm,
> still a tad manual ;) )
Do you want the account/sa/mbr to be automatically deleted when its expired
or out of time? This sounds a little severe, but I might not understand what
you are using it for.
> PS DALE: Congratulations on the new addition! Best wishes & happiness to
> you and your family!
Thanks. Its been challenging, to so the least. I always though that I didn't
sleep that much. Now I know what not sleeping much is like. :)
-- Dale E. Reed Jr. (email@example.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com