sederhananya gini: Welcome to DLL HELL hehehe...
persoalan ini terjadi karena pada waktu kita compile ulang DLL-nya, kita ga pake Binary Compatibily. jadinya file dll yang baru, punya nama yg sama dg yg lama tapi punya PID dan CLSID berbeda dg DLL yg lama.
best regards
[wwn]
On 3/6/06, thoyib <[EMAIL PROTECTED]> wrote:
----- Original Message -----From: Agus YudhiSent: Saturday, March 04, 2006 10:15 AMSubject: BILLINGPLUS ------ Run Time Error 438 - Object Doesn't Support this Property or Method
Dear Vbers,Saya punya program Billing ver 1.0 yg di install pada beberapa PC tidak mengalami masalah. Tetapi ketika program tsb di update ke ver 1.1 terdapat error di salah satu PC pesan errornya gini " Run Time Error 438 - Object Doesn't Support this Property or Method ".PC tsb sudah diinstall baik pakai NEW WINXP sp1 maupun WINXP sp2 dgn tmbahan install OFFICE XP saja.Kenapa ya ...? Ada yg bisa bantu..?Maap kalo p'tanyaannya bikin bingung (~_~)Berikut ini adalah penjelasan dr sitenya microsoft....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:193265 ( http://support.microsoft.com/kb/193265/EN-US/) PRB: VB Doesn't Generate Compile Error for Misspelled MethodsBest Regards,Agus Yudhi
IT Department
NYK Puninar Logistics Indonesia, PT
Jl. Cakung Cilincing Km. 1,5
Jakarta Timur 13910
Phn : 62 021 4608720
Fax : 62 021 4602280
Wahana Programmer Groups Links
<*> Untuk mengunjungi sponsor milis ini, klik link berikut:
http://wahanaprogrammer.net
<*> Untuk menghubungi owner milis ini, kirim email ke:
[EMAIL PROTECTED]
<*> Konsultasi pemrogramman bisa chat disini:
Yahoo! Messenger: wahanaprogrammer
SPONSORED LINKS
| Programmer | Indonesia | Basic programming language |
| Computer programming languages | Programming languages | Java programming language |
YAHOO! GROUPS LINKS
- Visit your group "Programmer-VB" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
