Run-time error 438

[misop]

Hi,

I just added some new code to my project. After this, I get error 438. It was everything good before adding this new code.

I added some code to automaticaly resize UserForm based on users screen resolution.

After this, my previos function FillData is dysfunctional.

Here is code ffrom Module:

Please Login or Register  to view this content.

[JapanDave]

Can you post a dummy workbook?

[misop]

You mean this attachment?

[misop]

Can someone help me?

[JapanDave]

Hey, I can't run the macro as it has Slovak characters. But it is giving me the same error when I run it.

This is all I can recommend at the moment.

From Microsoft website.

From Microsoft website:

Run Time Error 438 - Object Doesn't Support this Property or Method
The most common cause of error 438 is not maintaining binary compatibility between successive versions of your components. Each COM interface has an associated GUID that is called an interface ID (IID). Each coclass has an associated GUID that is called class ID (CLSID). When you compile an ActiveX component in Visual Basic, the CLSIDs and IIDs are compiled into the component's type library.
Example
A program that consists of a Visual Basic client and an ActiveX DLL is released to the user community. At a later time, additional functionality is to be added to the DLL component. The necessary modifications are made, and the ActiveX DLL is compiled without maintaining binary compatibility. When the DLL is released, the client that is trying to use the DLL will throw run time error 438. The reason this occurs is that when the DLL was compiled, a fresh set of GUIDs was compiled into the DLL, and the client has no reference to these new GUIDs. This is why it is important to maintain binary compatibility with the last-released version of the component when you are trying to release a newer version.

Another example for the runtime error 438 would be including the wrong version of Microsoft Data Access Components (MDAC) in the distribution package. For example, a Visual Basic 6 Service Pack 5 program is built on Microsoft Windows 2000 Service Pack 2 by using the latest version of MDAC that is present (version 2.6). When the distribution is built, an earlier version of MDAC (version 2.5) is used (unless MDAC 2.6 is downloaded), causing an error 438 to be thrown when the distributed program is run.

Another scenario would be misspelled method or property names, and this scenario is described in the following Microsoft Knowledge Base article:

This may be as simple as adding a reference for the ActiveX data Access Object that the older Access database would have used created.
For instance if you are now using Excel 2003 as a database with ADO2.8 library and the Access records were created using ADO2.4 (as an example). The differences within the newer library may not be supported.
By adding a reference to the older ADO dll that the Access database used to create the records this may fix the issue.