This property does always exist, but is also means that you need to know it: If you really want to play safe, use the ‘. The code stops running as soon as ‘ lItem’ matches the index of the missing reference:įor lItem = 1 To Name‘ property does not exist for missing references, so as long as the item’s counter is smaller than the missing reference item you are indeed able to query this property. Set oReference = (1) ' Usually VBA is number 1Įven next code may trigger the error. However, if you use a numeric index to obtain a reference object, the error does not trigger. Using a named index with missing references triggers the error. Suppose you want to set a reference to “Visual Basic for Applications” then you would write the following statement (“VBA” is the codename for this reference): The funny thing is that a missing reference impacts on your code when addressing the other references in the project.
When the ‘Automation error Library not registered.’ triggers on registered libraries When you close the compiler error, VBE will open the references dialog for you. If there is a missing reference, VBE may make this problem evident by issuing a compile error “ Can’t find project or library” on a function that you know is correct (I had that on the String() function, not to confuse with VBA.String()). Tip: before you distribute your application, run a compile (Debug -> Compile).
To correct the problem, open the VB-IDE, go to your project references (Tools -> References), either scroll the list and put or remove a checkmark in front of the desired component or browse for a file on your disk.Īh, if you have access to the project, otherwise you’re out of luck. If this occurs, then you will see such “MISSING” reference. But there are cases where the component does not correctly remap (because the GUID has changed or because it is not available). In general, each reference is correctly mapped to the right -and probably also most recent- component, since the GUID of each application does not change. Obviously, you should never distribute applications without making sure that the components used are available on the target computers, but there are cases in which VBA takes care of resolving the problem automatically, one example are the Microsoft Office applications, where each version installs in a separate folder containing a number (for instance for Office 2003 (Release 11) you have C:\Program Files\Microsoft Office\Office 11) This is the case when for example a DLL, OCX or another VBA project used while developing in your application is not installed on the computer the application is being used. If you encounter the VBA Run-time error ‘Automation error Library not registered.’ then between your VBA project’s references there is a reference to a file that is “MISSING”.
0 kommentar(er)
