asked on

Unable to register ACtiveX control in Access

I have an ActiveX control that was operating prior to a WindowsXP rollout.
I have successfully installed the ocx using regsvr32.exe.
However, the control does not appear in Access. When I try to add it using the Tool | ActiveX Controls... option I get the error message:

WebviewX2.ocx was unable to add/remove itself to/from your system. Install/remove the control using a seperate setup utility.

Adding the ocx to the Modules reference list did not make any difference.

Any ideas what might be causing this behaviour?

Thanks.

jjafferr

Hi, use this example:

Animated GIF's in Access

You will need an ActiveX control for this.

Go to this location:
ftp://ftp.simtel.net/pub/simtelnet/win95/graphics/
Scroll down through the list and download: agv10.zip
This zip file will contain 3 files. The only one you will need is: Gif89.dll

Place Gif89.dll in your C:\Windows\System folder and register it by typing the following in the Start, Run box:
C:\Windows\System\Regsvr32.exe C:\Windows\System\Gif89.dll

You need to then Register this ActiveX in Access. Open Access and open the TOOLS menu and choose ActiveX Controls. Next click register, change the file type from ocx to dll, and browse for the "Gif89.dll" file in the C:\Windows\System folder. Click on it and then choose register.

To use this new control in Access, open your form in design view then choose the "INSERT" from Access main menu, then ActiveX Control and choose "Gif89 Class". This will place a gif object on your form. The last property of this control (bottom of list) is called "File Name". Here is where you enter the complete path to the .gif file you wish to use. There is also a property that allows you to embed or link the file. Remember that if the file size is large you may want to link it over embedding it to save overhead in your database.

Special Note:
One thing to remember is if you wish this Animation to work on a different machine, you must also place a copy of the gif89.dll (again in the Windows/System folder) in the different machine and go through the registering of the dll as described above. This can be a pain to remember, but the finished product is very appealing.

jaffer

ASKER CERTIFIED SOLUTION

Scott McDaniel (EE MVE )

membership

This solution is only available to members.

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

Start Free Trial

Greenbase

ASKER

I'm not sure. I did need to get the IT department to log in as Administrator to register the ocx on the machine. Do you think I need to get them to log-in to register within Access itself? I'll tell you, the more security they put on the machines the more it gives license for nonsensical bureaucracy. I used to be able to do all this by myself. I guess I'll give this a try and see.

Scott McDaniel (EE MVE )

You shouldn't have to ... if the control is registered, you are merely telling access to use it ...

Greenbase

ASKER

The problem was occuring because if full security in XP is switched on, there is now a security layer around each new OCX or DLL you want to install. Had my clients upgraded to power users by IT and the problem went away.