ocx are not working ... 1

[remco5897]

Hi,

I have an Access application which uses several .ocx's (non Microsoft) like a list box and a control which emulates the Outlook bar.

On the development machine they work great but on another machine I get run time errors which I can not understand, when I try to run a form which contains them. I just see the empty containers.

Now the strange thing is, is that I can access the properties and methods in design time but I can not put a complete new one on a new form while it is in the list of activeX controls!?!? It just won't show up. What could be wrong?

Being in the list of activeX controls leaves me to believe that the controls are properly registered. Could I be wrong?

Compiling the code works fine but when I am debugging the run time errors the vba engine tells me it can not find an object which is the first .ocx which the code is initialising.

An installation on a brand new machine has the same problem so the application is only running on the development machine.

It seems then obvious that there are some libraries missing or something like that. I just can not figure it out!

It was easy to check that the machines had all the necesary libraries because I compile them myself so I know what is being referenced.

Any idea what is wrong?

Other info:

All 3 machines have Windows XP proffesional and Office XP pro.

The development machine has extra development tools; Visual Studio and the ,NET frame work with C#.NET and VB.NT.



All machni

 

[faeryfyrre]

Tricky problem you have there.

From what i understand you've only installed the .NET framework on your development machine.
Maybe the OCX controls reply on the .NET framework??

Just a suggestion.

Alec Doughty
Doughty Consulting P/L

"Life's a competition. Play hard, but play fair"

 

[remco5897]

Hi faeryfyre,

Thanks for the reply.

I compile the .ocx's myself using Visual Studio. Just like in MS Access you have to indicate which references you want to include.

I checked the other machines and all the references (.ocx, .dll, etc) are also installed on the other machines. I even registered them myself using the command prompt.

I do not get an error that a particular .ocx or .dll is not found or installed.

Anymore suggestions?

 

[JeffTullin]

Could this be a licence file issue?
eg Licenced for use in run-time but not in design time?

I dunno if VS has a licence file default for OCX files, but I have run into this before with commercial OCXs

 

[remco5897]

Thnx for the tip Jeff, I am going to check it out and let you know.

 

[faeryfyrre]

This is only an educated guess but, do you use Visual Studio .NET to compile your OCX's? If you do then i think you will need to install the .NET Framework on your client machines before the OCX's will work properly. That's not to say they won't install and register properly on the Client machines and thus appear in the References Library but you wouldn't be able to properly use the new controls until the Framework is installed on the Client Machines.

Can't hurt to try installing the .NET framework on one of the clients to see if i'm right can it?

Cheers

Alec Doughty
Doughty Consulting P/L

"Life's a competition. Play hard, but play fair"

 

[remco5897]

Jeff: still trying to find out about the licencing issue.

Alec: Tommorow (saturday) we are going to format two machines (for testing purposes) and we will install the framwork on one of them to see what is going to happen.

You are right, it doesn't hurt.


Anyway, I am really appreciating your input guys, because this is driving us up the wall. For some reason we return to the thought that the ocx's are not compiling correctly.

Keep you informed and hope we have some luck with this! We installed it on several more machines; all have the same problem. This somehow settles me down because it is starting mean that we are indeed having a situation were the development machine has something installed which the others haven't.

Remco

"I'm a great believer in luck, and I find the harder I work, the more I have of it."

Thomas Jefferson (1743-1826), author of the Declaration of Independence

 

[remco5897]

Alec,

We have solved the problem. You were right in a sense (so a star for that), we needed to install a development framework but it wasn't .NET but it was an earlier version of Visual Studio.

The missing .dll was part of an earlier Visual Studio runtime which used to be installed on the development machine and was not included in the install procedure.

Can you believe it.

Anyway thanx for the responses, it certainly helped us looking in the right direction.

Remco

 

[faeryfyrre]

Glad to help.

Microsoft strike again eh? Wierd Dependencies R US

Alec Doughty
Doughty Consulting P/L

"Life's a competition. Play hard, but play fair"