No. What I would recommend is:
* creating a new DB called EmerladCalls
* copying the Calls table to the new db
* create a view named Calls in the Emerald Database that is:
Select * From EmeraldCalls..Calls
* make sure all the users exist in the EmeraldCalls db (they don't
have to have access to the Calls table).
* Make sure all users have read access to calls (view), and that
EmeraldApps has insert permission to calls (view).
* Modify the Trigger on the New calls table (from insttrig.sql)
to update the Emerald..ServerPorts and Emerald..SubAccounts tables,
This will keep the calls data out of your Emerald database, and keeps
things a lot cleaner. It also lets you do what you want.
Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart