Sorry it took me so long to get back to this. Its not an easy
problem to find. I did some tests in the lab and I think I
figured it out. Running charges uses the tempdb quite a bit.
Depending on the size of your calls table and the number of users
you have, depends on the size you need for your tempdb.
The lab machine only had like 2 megs for its tempdb. When I copied
a production machine's DB to it (with 215,000 stop records in the calls
database and about 4500 users) it wouldn't run. Uping the tempdb
to 15 megs allowed it to work.
Moral of the story: Add about 10 megs to your master database device,
expand your tempdb, and it should work.
-- Dale E. Reed Jr. (email@example.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com