asked on

Registering DLLs and Creating Program Groups with Access 2003 Developer Extensions

I am using Access 2003 Developer Extensions to develop and distribute a software product built in Access 2003. I have two questions:

1. What's the easiest and least expensive way to specify that a copy of the required DLL files be placed in the C:\Windows\system32 directory, as opposed to the program's installation directory, and then registered on the PC that it is being installed on.

2. I am installing several utilities (also built in Access 2003) via chained installations. Each utility has its own mdb and icon. I want to create a program group that is accessible from the Start Menu and/or Desktop that contains an icon for the software product as well as one for each of the utilities being installed. So far I have only been able to create individual icons, that are accessible fromthe Start Menu and/or Desktop

ASKER CERTIFIED SOLUTION

rockiroads

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

kcetv

ASKER

Thank you for your response. I know how to use the regsvr to manually register a file. However, I am creating an installation CD to distribute to clients and I don't want them to have to manually register the dlls.

I am using the 2003 ADE's to create the installation CD, and I was hoping someone could help me figure out how to automatically move the DLLs to the location clients are use to having them in and then register them. The problem with the ADE is that it automatically installs all the files in the same location.

I have a batch file that I created based on another post to the EE group that does this but I was just wondering if there was another, easier way to do it.

SOLUTION

dannywareham

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rockiroads

NSIS is a scripting language, it should be able to do what u ask