Griff,
lets for a moment believe the situation is this software was programmed for his company by an employed developer. So the software is his property, including sources.
Fadiikhan,
it seems the developer you may have fired or who moved to some other company has left some revenge. Or try to remember, did you aks for such a ssecurity mechanism in your software? I think, Fadiikhan, you have to deal with your developer about this. We can't judge what's fair in this case or not. It's a somewhat unfair move to leave a software with such a ransom locking mechanism, but you haave the sources. Maybe he's just telling you in a roundabout way, that you don't get far without a hired developer.
So, as you seem not to be a developer, hire one. Maybe that was his intention. If it wasn't simpy you to ask for the feature. Anyway, you now have to deal with this.
Maybe you still just got as far as decompiling a software you once bought but only licensed for a year. It just shows what many say about software securing mechanisms through encryption. Even if someone finds a decompiler and uses it, he still hasn't the knowledge of all the code, you have to work into it, if you're no devloper, you're lost. It's like being able to decrypt a text, but still don't understandit in its cleartext form.
Now even if I would like to help you for reasons of "in dubio pro reo", I couldn't. You have your good reasons to do what you do, but the code in question could be anywhere in the sources. The simple answer is: If you "speak" Foxpro" you sure could find an remove it, once you have the sources. But it might also be encapsulated in a DLL that's not done in Foxpro, too, to make it even less easy to crack.
Chriss