run-time error 438 on client machine when delivering database

[nowickil]

Hi,

I have a project that I've delivered to this customer in the past. They recently upgraded from Access 97 to Access 2000. We went through the upgrade with minor issues that I was able to resolve, compile at my site, and then deliver to the customer site. Then they requested another minor change. I implemented that change, compiled again, and tried to deliver the database. When I try to open the database on the other machine, I'm suddently getting a run time error 438 telling me that 'the object does not support the property or method'. The line of code in question is:

me.ActiveXCtl10.ShowOpen

I was thinking that I must have a reference problem. Sure enough, on my machine I was referencing the Microsoft ActiveX Data Objects 2.7 library, but on the other machine, they only had the 2.5 version. I changed my reference to the 2.5 version, recompiled, and tried again. Same problem.

The change I made had nothing to do with this particular control - I didn't even touch this form. I'm sure this is some kind of a reference issue, but I'm stuck.

Any suggestions?

Thanks,

LeAnn

 

[nowickil]

I finally resolved this and am updating this thread in case anyone else out there ever has something similar happen.

The problem was that comdlg32.ocx was missing from my machine. This file is necessary to use the common dialog MSComDlg.CommonDialog.1. A related file, comctl32.ocx, was still there, but comdlg32.ocx was gone, and no entry in the registry for it either. Once I found that this was indeed missing from my machine, I did a full reinstall of Visual Basic. I verified the comdlg32.ocx was back in place and had the appropriate entry in the registry. Now everything works as it should. I have no idea what happened to cause this file to disappear, but things are working for now. Anyone who has any theories on the unexplained dissappearance of comdlg32.ocx, feel free to respond...

L.