Microsoft Direct Speech won't run on client machine

Question

0.00/5 (No votes)

See more:

I've built a program that uses the Microsoft direct speech control. It works fine on the machine I designed it on, but when I install it on the client machine it throws an error saying "You do not have an appropriate licence to use this functionality". So I did a Google search and found something called VB6cli.exe which is supposed to fix faulty licencing issues in vb6. It didn't. I also removed all references to the direct speech control, rebuilt the program and its setup, and it installed and ran just fine on the client machine. So I've narrowed it down to that control being the problem.

Basically I'm just wondering if anyone out there is aware of this issue and how they fixed it. Thanks in advance.

Posted 20-Dec-11 7:18am

Kevnar

Updated 20-Dec-11 7:21am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

#realJSOP · Accepted Answer · 2011-12-20T07:52:00

Solution 1

Make sure that both you and your client have the latest version of SAPI installed (you may have to install the latest sdk as well if you need to update your installation).

Posted 20-Dec-11 7:52am

#realJSOP

Comments

Kevnar 20-Dec-11 14:01pm

Yes, that fixed it. I'd just discovered that solution myself and I came to post the answer, but you saved me the trouble. I'll have to include the sapi package in the distribution. Thanks.