Maximizer Business Partner Window not loading

What happens if you grant them Power Users permissions?

The Machine is a Windows 2000 domain controller, it doesn't have the concept of power users.

>The [Terminal Server] is a Windows 2000 domain controller

Oh. That's not recommended practice.

>I've granted full access rights to c:\program files\Maximizer and
>still no joy....

Well, for testing purposes at least, you could try granting users full permissions to %SystemRoot% (and subfolders) and all Maximizer-related registry keys (and subkeys).

[This message was edited by Gord Thompson on March 12, 2004 at 11:40 AM.]

After playing around with VMWare and a copy of XP I've discovered that Power Users can run the window.

After alot of digging (read swearing), I've tracked Maximizers behaviour down to.

Find the DLL in BPWindow and Call DllSelfRegister. If this fails don't load the module.

The current solution is to use regsvr32 as administrator to register the dll and then run maximizer with the command prompt /DebugBP

This tells maximizer to not try and register the file but use existing registration so that you can debug your window from your IDE (ie VB6).

If anyone has any other ideas of a more elegant solution to this please let me know.

Try granting your users the following permissions on the HKEY_CLASSES_ROOT registry key:

I'll give it a go, I just wanted to avoid giving the users too much power!!! They have a definite tendancy to break stuff

Finally solved it. Maximizer tries to register the business partner ocx.

If you run maximizer with the debug parameter it will simply use the the control you have already registered as administrator.