General discussion

Locked

Open file dialog in runtime access 97, e

By robert.f.collins ·
I am getting an error: Object doesn't support this property or method, When attempting to open a common dialog get open file in a runtime access 97 database created using wise installer with a sagekey script. The libraries are there, after install there is no prompt for a reboot, the application works great otherwise. The application always works on the development machine. and not on others. Win95 is the operating system. The get/open file dialog needs to be there for the users. Why amI getting this error and most importantly, how do I fix this now!

This conversation is currently closed to new comments.

8 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Open file dialog in runtime access 97, e

by mcorr In reply to Open file dialog in runti ...
Collapse -

Open file dialog in runtime access 97, e

by robert.f.collins In reply to Open file dialog in runti ...
Collapse -

Open file dialog in runtime access 97, e

by mcorr In reply to Open file dialog in runti ...

I have had problems with this also, and I even have an open question on this forum with no useful responses.

I think the problem is the dll you are trying to use is not registered. In my application I have to manually register the control on each PC after installation. This may or may not be a solution for you, since I only had three PCs to roll out to.

Collapse -

Open file dialog in runtime access 97, e

by robert.f.collins In reply to Open file dialog in runti ...

The libraries were all correctly registered. It would not function if the properties were set on the control's custom properties dialog box. It did work if the properties were set in code from the module that called the functions.

Collapse -

Open file dialog in runtime access 97, e

by Todd Parker In reply to Open file dialog in runti ...

For lack of response, I will offer an experience of mine. I've gotten the same exact error, but with a different reference. What i found (in my case) was that the clients have one or two problems. They either have multiple mismatched DLL's by the same name on the hard drive, or the same scenario but in the registry. This will cause the error every time. What I did to get around it? I placed explicit referencing everywhere in my code that called that reference. For instace: instead of calling Date(), you would call VBA.Date()

Good luck,
-Parker

Collapse -

Open file dialog in runtime access 97, e

by robert.f.collins In reply to Open file dialog in runti ...

The libraries were all correctly registered. It would not function if the properties were set on the control's custom properties dialog box. It did work if the properties were set in code from the module that called the functions.

Collapse -

Open file dialog in runtime access 97, e

by LyXX In reply to Open file dialog in runti ...

May be problem not in dialog. If you using ADO control for access to Data, you need install MSDAC first.
For detailed solution problem you need determinate in which sring of code error is raised. For example you can using msgbox, and see after which of it error pop up.

Collapse -

Open file dialog in runtime access 97, e

by robert.f.collins In reply to Open file dialog in runti ...

The libraries were all correctly registered. It would not function if the properties were set on the control's custom properties dialog box. It did work if the properties were set in code from the module that called the functions.

Back to Web Development Forum
8 total posts (Page 1 of 1)  

Software Forums