also when they show up for a sec i can see that the whole column is in 0...






>>but there is another problem with that there ate calls like 911 or 411 calls made that they do need to be showed up in the screen..
>>now i have one customer that made 2 411 calls and those are the only ones whowing up..
>
>Go back to the base logic of the application; the DO CASE...ENDCASE switch is set to filter out anything that doesn't start with "0", "1", or "#". To deal with these new requirements, you need to add CASE entries to the table to the DO CASE...ENDCASE to handle them. For example, you could add the following in the DO CASE...ENDCASE to handle the "411" and "911" calls with a fixed rate of $0.75 and $10.00 respectively:
>
>

*  insert just befor the OTHERWISE clause
>   CASE LEFT(view1.dialednr,3) == "411"  && the dialed number was 411
>      * 411 calls cost $0.75 each
>      lnResult = .75
>   CASE LEFT(view1.dialednr,3) == "911"
>      *  911 calls cost $10 each
>      lnResult = 10.00

>
>You can continue this approach for as many things as you need; this change forces the rate for specific numbers If you needed to handle things to do lookups in the rate table rather than hard-coding the rate as shown, you could change the code to set the lcSeekValue, forcing a lookup.
>
>For example, to force any number where the second and third digits were "11" to do a 3 character lookup, instead of the code shown above, substitute:
>
>

*  alternative to test second and third character and
>*   force a 3 character lookup
>   CASE SUBST(view1.dialednr, 2, 2) == '11'
>      *  take the first three characters if the 2nd and 3rd are "11"
>      *  and a previous case didn't handle the number already
>      lcSeekValue = LEFT(view1.dialednr,3)

>
>>can you please help me correct this.....i know tht is halfway working..
>>what i did on the view is i fileter all the dialednr that are in blank....we dont need them anyways...