VoiceGuide IVR Software Main Page
Jump to content

The "100 Bug" In Lib_num2wav, Hundreds2wav Function

Recommended Posts

In the lib_num2wav script : hundreds2wav(ByVal AmountToSay) function there is a bug.

If the number to say ends with 100, 200, 300 etc., an unnecessary comma will be added after the hundred.wav file.

The problem is in this line, which is close to the end:

Result = Result & "," & s2_WavList

s2_WavList is empty in case of 100, 200 etc.

 

 

Furthermore, if the number is e.g. 300400 the extra comma problem comes after each hundred file

Here is my solution : add the foolowing condition around the Result = .... line

 

If s2_WavList <> "" Then

Result = Result & "," & s2_WavList

End If

Share this post


Link to post

Have you found that that extra comma affects things? Or is it just basically ignored with the next specified file being played?

Share this post


Link to post

It did not cause any trouble and I fixed the problem for myself. I had two commas next to each other in a sequence of wav files. I do not know, however, whether it can cause problems for others in other situations.

Share this post


Link to post

Two (or more) commas should not cause a problem. VG should skip over the unspecified file(s) and play the next file in the sequence.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×