I will try my best to answer your questions.
> Last Night around 4:00 in the morning, I ran the CALL CONSOLIDATION, I
>didn't get any error messages for this , and it said it completed fine. I
>am running emerald 2.11.1,
This is the problem... 2.1.11 does not do the call consolidation correctly.
The data that you hoped would be saved is now gone forever. Dale says
that 2.2.38 does it right, but don't count on it. It is better to create a
script that will delete the start records, and run it from iSQL.
> Another issue that seems to still be present is connections to the SQL
>database. After exteneding the ammount of connections to the database from
>15 to 60 , I don't get the errors quite as often as I use to, but I still
>get the error's just now every 2 weeks or so instead of every 3 days or so.
How many users and radius machines are you running? 60 should be plenty.
Try alocating more ram to SQL, (I have 8192, but plan on drasticaly
increasing it soon. Set open databases to 20, open objects to 500, locks
to 10,000. I have 5 people using Emerald, & 2 radius machines and have
user connections set to 45 with NO problems.
> Another question we have is entering Credit card info into the database,
>it only seems to work from one computer in our office.
Make sure that when you enter the cc number that you do NOT select the card
type, let Emerald figure it out by itself. The card types in the pull down
box are incorrect.
>Please can anyone help me.
This isn't much, but I hope it helps...
John C. Lange, Sr. PALACE dot NET, INC.
firstname.lastname@example.org MICRO-TECH Computers, Inc.
608.742.1601 & 6980 2800 New Pinery Road
http://www.palacenet.net/ Portage, WI 53901
Visit our online store @ http://www.microt.com/
Authorized iPSwitch WebVar @ http://www.microt.com/iPSwitch/index.html
--- _-\<,_ Fastest Service in Town
--- (_)/ (_)