not licensed system

[vans324]

vb6 custom app works on 1 windows xp workstation but when we transferred the folder with the exe custom app it doesn't work on other PC's with windows 7 and windows xp. When we open the VB6 custom application it gives a message "not licensed system". Anyone can shed light on this? sorry if this sounds like a stupid question I really don't have a clue.

[baja_yu]

I'm confused a bit. Let's get some things cleared first.

1. Did you make the application? (do you have the source code)
2. What is the exact text of message you described with "not licensed system"? (a screen shot image would be nice)
3. Don't you have a proper installer for deploying the application rather then just copying the folder? Does the application have any dependencies beyond the basic VB6 runtime?

[vans324]

I'm confused a bit. Let's get some things cleared first.

1. Did you make the application? (do you have the source code)
2. What is the exact text of message you described with "not licensed system"? (a screen shot image would be nice)
3. Don't you have a proper installer for deploying the application rather then just copying the folder? Does the application have any dependencies beyond the basic VB6 runtime?

Thanks for taking the time to respond to my query.

1. We don't have the source code. It's a company bought custom application. Company supervisors wanted us to use the same app in our computers.

2. exact error message is "filename not licensed system" sorry can't provide you a screenshot.

3. As told, application doesn't have and doesn't need an installer. The required dependencies is included in the folder.

[baja_yu]

You obviously need to purchase a license for every computer you install it on. I'd suggest contacting whomever you bought it from.

[vans324]

Thanks, that's what we suspected all along.

[dilettante]

3. As told, application doesn't have and doesn't need an installer. The required dependencies is included in the folder.

I don't buy it. The installer normally puts the license in place unless the program does some kind of runtime activation.

It may also do all sorts of other things like check for prerequisites; set up data folders, set security on them, and copy files into them; register components; define shortcuts; etc.


But yes, the upshot is you'll need to get in contact with the source of this application.