By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,471 Members | 2,264 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,471 IT Pros & Developers. It's quick & easy.

Common Dialog Control Error

P: 22
Hi All

I have written an Access Database Application with the use of VB6 that makes use of the “CommonDialog” ActiveX control to call a Browse File facility. Because I have Visual Basic 6.0 installed on my system all the function works fine.

The problem occurs when another user who has not got Visual Basic 6.0 in their system comes to use the same application. When they use the browse facility an error message “438 Object doesn’t support this property or method”.

At first I believed that the issue stemmed from a problem with the references that Access was using but upon matching both systems to use the same reference the same error occurs.

Any Ideas?
Feb 16 '07 #1
Share this Question
Share on Google+
9 Replies


Rabbit
Expert Mod 10K+
P: 12,315
I'm not sure but I think compiling the code should solve your problem.
Feb 16 '07 #2

ADezii
Expert 5K+
P: 8,597
Hi All

I have written an Access Database Application with the use of VB6 that makes use of the “CommonDialog” ActiveX control to call a Browse File facility. Because I have Visual Basic 6.0 installed on my system all the function works fine.

The problem occurs when another user who has not got Visual Basic 6.0 in their system comes to use the same application. When they use the browse facility an error message “438 Object doesn’t support this property or method”.

At first I believed that the issue stemmed from a problem with the references that Access was using but upon matching both systems to use the same reference the same error occurs.

Any Ideas?
Wouldn't a VB 6 Setup/Installation Package solve the problem?
Feb 16 '07 #3

nico5038
Expert 2.5K+
P: 3,072
You found out why I never use ActiveX controls :-)
You'll need to trace the .dll and/or the .ocx control used and transfer that together with your application to make sure it will work on every PC.
An alternative might be to use the Developer edition to create a package that will include the .ocx control, but you could also try to use the windows class modules from:
http://www.mvps.org/access/modules/mdl0013.htm

Nic;o)
Feb 16 '07 #4

P: 22
I'm not sure but I think compiling the code should solve your problem.

The code is fully compiled, all other functions run apart from the function that requires the Common Dialog Control. Im still thinking that it has something to do with references.
Feb 19 '07 #5

P: 22
Wouldn't a VB 6 Setup/Installation Package solve the problem?
I would very much like to install VB 6 on the other systems, but then there is the small issue of licences that would need to be considered, which i do not have.
Feb 19 '07 #6

P: 22
You found out why I never use ActiveX controls :-)
You'll need to trace the .dll and/or the .ocx control used and transfer that together with your application to make sure it will work on every PC.
An alternative might be to use the Developer edition to create a package that will include the .ocx control, but you could also try to use the windows class modules from:
http://www.mvps.org/access/modules/mdl0013.htm

Nic;o)
Thank You, after reading you post I was slightly optimistic about getting this issue sorted but after having transferred the "COMDLG32.ocx" file used on my system and placed it in the system32 folder on the other system, but the problem still remains. I also matched the other systems references to those of the working system, but still no joy.

I also took a look at the file from the link you gave me, but it’s too complex and requires a greater amount of user input for what my system is required for. My system makes use of the FindFirstFile function, which takes the user directly to the file area they require based on what parameters are passed to it.

As another way to try and solve this issue I then tried to replace the control on the other system, by deleting and then recreating it, this then presented me with a run time licence error.

And ideas of what path to take from here?
Feb 19 '07 #7

debasisdas
Expert 5K+
P: 8,127
this problem i sbecause of the missing ocx file
since vb 6 is not installed in other pc its not working
to solve this u need to create the setup and install in that system.
simply compiling the EXE will not work

still if the problem persists copy that OCX file to the system32 folder and register the file with windows by using REGSVR32 key

at RUN

REGSVR32 'complete path of the file'


difinately it will work
Feb 19 '07 #8

P: 22
Thanks for you help but I’m sorry to say that the problem is still not fixed. Is their any setting within Access, which may prevent the ActiveX controls from working?

The reason why I say this is because I have another totally separate database application on both systems, which uses the same ActiveX control and it works perfectly.
Feb 19 '07 #9

P: 22
THANKS for all the help. I managed to solve the problem by creating a dummy form with a Common Dialog Control and basic file browse function. I then loaded that along with the rest of the database onto the other system, from there I recreated the form I needed using the dummy form on the second system and it now works! Though I still don’t know why the form/code did not work in the first place. Ah well – All’s well that ends well. Thanks again
Feb 19 '07 #10

Post your reply

Sign in to post your reply or Sign up for a free account.