You could do this today with Emerald, although its not a native feature.
Add a trigger to the MasterAccounts table, and have it check the fields
you want with a set of tables you define to hold the data. If a match
is found, use the RAISERROR SQL function to error the insert. Emerald
will trap the error and display it to the user.
> Another Idea that past through my ears is a feature called Global
> Blacklist/Ban List. This feature can make any ISP running Emerald to update
> the global ISP Blacklist/Ban List by having the SQL server to copy certain
> fields of Data from their server to IEA's Global Blacklist Server (should
> IEA be interested in adding one) therefore ISP's can protect themselves from
> clients who hop from one ISP to another without paying or who has broken TOS
> agreements and got banned. The reason why I say Ban list and Blacklist are
> defined as follows:
> Ban: a Client who has not upheld the TOS agreement and caused illegal or
> harmful activity over the Internet connection.
> Blacklist: a Client who has not paid clients for services rendered and would
> be capable of doing the same at another provider.
The liability on this is fairly great. It would be much like the
Credit Beareu here in the states. Undoubtly, someone would sue us for
on a list that we ourselves have no real control over. This is much
the spam lists today. We might think about the means, but would not
to be apart of managing it.
Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com