[es] - Koristenje MS Accessa bez office-a

mld

Član broj: 156249
Poruke: 274
*.adsl-2.sezampro.rs.

+13 Profil

Re: Koristenje MS Accessa bez office-a

^{18.09.2012. u 09:26 - pre 141 meseci}

Proveri da li ti nedostaje neka od Active X komponenti, komponente koje su sadržane u MS MDAC(Microsoft Data Access Components) koje obezbedjuju pristup bazi ili je u pitanju neki od MS Frameworka koji ti nedostaje.

To takodje može da ima veze sa različitim verzijama prilikom kompajliranja evo jednog mogućeg objašnjenja:
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.

_{[Ovu poruku je menjao mld dana 18.09.2012. u 10:36 GMT+1]}

Odgovor na temu