469,323 Members | 1,583 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,323 developers. It's quick & easy.

Sharing database creating error messages for missing or broken ref to mscomct2.ocx

I placed a database on the server and all of the other users are receiving the error message:

Your Microsoft Access database or project contains a missing or broken reference to the file 'mscomct2.ocx' version 2.0

This is a virtual network and we are all running our own copies of Access.

I did use several ActiveX controls. Can anyone tell me what the other users need to do? Is there a download they can perform?

Thank you!
Mar 29 '07 #1
4 11164
MMcCarthy
14,534 Expert Mod 8TB
I placed a database on the server and all of the other users are receiving the error message:

Your Microsoft Access database or project contains a missing or broken reference to the file 'mscomct2.ocx' version 2.0

This is a virtual network and we are all running our own copies of Access.

I did use several ActiveX controls. Can anyone tell me what the other users need to do? Is there a download they can perform?

Thank you!
You need to open the VBA editor on each machine and see if any of the libraries are marked as missing on the references list. It's possible these users don't have the libraries you used available on their lists.

Mary
Mar 29 '07 #2
ADezii
8,800 Expert 8TB
I placed a database on the server and all of the other users are receiving the error message:

Your Microsoft Access database or project contains a missing or broken reference to the file 'mscomct2.ocx' version 2.0

This is a virtual network and we are all running our own copies of Access.

I did use several ActiveX controls. Can anyone tell me what the other users need to do? Is there a download they can perform?

Thank you!
Here is a code snippet that you can utilize to Reference References (light humor). At least it will give you some status information pertaining to the References on each machine:
Expand|Select|Wrap|Line Numbers
  1. Dim MyRef As Reference
  2.  
  3. For Each MyRef In Application.References
  4.   Debug.Print "Reference Name: " & MyRef.Name
  5.   Debug.Print "Is the Reference Built-In: " & IIf(MyRef.BuiltIn = True, "Yes", "No")
  6.   Debug.Print "Full Path of reference: " & MyRef.FullPath
  7.   Debug.Print "Version Number: " & MyRef.Major & "." & MyRef.Minor
  8.   Debug.Print "Kind of Reference: " & MyRef.Kind
  9.   Debug.Print "Is the Reference Broken?: " & IIf(MyRef.IsBroken = True, "Broken", "Intact")
  10.   Debug.Print vbCrLf
  11. Next MyRef
Typical Output:

Reference Name: VBA
Is the Reference Built-In: Yes
Full Path of reference: C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL
Version Number: 4.0
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: Access
Is the Reference Built-In: Yes
Full Path of reference: C:\program files\microsoft office\OFFICE11\msacc.olb
Version Number: 9.0
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: stdole
Is the Reference Built-In: No
Full Path of reference: C:\WINDOWS\system32\stdole2.tlb
Version Number: 2.0
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: DAO
Is the Reference Built-In: No
Full Path of reference: C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll
Version Number: 5.0
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: ADODB
Is the Reference Built-In: No
Full Path of reference: C:\Program Files\Common Files\System\ADO\msado21.tlb
Version Number: 2.1
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: MSACAL
Is the Reference Built-In: No
Full Path of reference: C:\PROGRA~1\MICROS~4\OFFICE11\MSCAL.OCX
Version Number: 7.0
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: Office
Is the Reference Built-In: No
Full Path of reference: C:\Program Files\Common Files\Microsoft Shared\office11\mso.dll
Version Number: 2.3
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: ComCtl2
Is the Reference Built-In: No
Full Path of reference: C:\WINDOWS\system32\COMCT232.OCX
Version Number: 1.1
Kind of Reference: 0
Is the Reference Broken?: Intact
Mar 30 '07 #3
Here is a code snippet that you can utilize to Reference References (light humor). At least it will give you some status information pertaining to the References on each machine:
Expand|Select|Wrap|Line Numbers
  1. Dim MyRef As Reference
  2.  
  3. For Each MyRef In Application.References
  4.   Debug.Print "Reference Name: " & MyRef.Name
  5.   Debug.Print "Is the Reference Built-In: " & IIf(MyRef.BuiltIn = True, "Yes", "No")
  6.   Debug.Print "Full Path of reference: " & MyRef.FullPath
  7.   Debug.Print "Version Number: " & MyRef.Major & "." & MyRef.Minor
  8.   Debug.Print "Kind of Reference: " & MyRef.Kind
  9.   Debug.Print "Is the Reference Broken?: " & IIf(MyRef.IsBroken = True, "Broken", "Intact")
  10.   Debug.Print vbCrLf
  11. Next MyRef
Typical Output:

Reference Name: VBA
Is the Reference Built-In: Yes
Full Path of reference: C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL
Version Number: 4.0
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: Access
Is the Reference Built-In: Yes
Full Path of reference: C:\program files\microsoft office\OFFICE11\msacc.olb
Version Number: 9.0
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: stdole
Is the Reference Built-In: No
Full Path of reference: C:\WINDOWS\system32\stdole2.tlb
Version Number: 2.0
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: DAO
Is the Reference Built-In: No
Full Path of reference: C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll
Version Number: 5.0
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: ADODB
Is the Reference Built-In: No
Full Path of reference: C:\Program Files\Common Files\System\ADO\msado21.tlb
Version Number: 2.1
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: MSACAL
Is the Reference Built-In: No
Full Path of reference: C:\PROGRA~1\MICROS~4\OFFICE11\MSCAL.OCX
Version Number: 7.0
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: Office
Is the Reference Built-In: No
Full Path of reference: C:\Program Files\Common Files\Microsoft Shared\office11\mso.dll
Version Number: 2.3
Kind of Reference: 0
Is the Reference Broken?: Intact


Reference Name: ComCtl2
Is the Reference Built-In: No
Full Path of reference: C:\WINDOWS\system32\COMCT232.OCX
Version Number: 1.1
Kind of Reference: 0
Is the Reference Broken?: Intact

1) Being a VBA newbie, where do I put this in the VB Editor?

2) Where and when will it run? I am assuming upon opening the database?

3) If the references are not intact, how do I proceed?

4) Is this something that is recommended any time I create a shared database?

Thanks!
Mar 30 '07 #4
ADezii
8,800 Expert 8TB
1) Being a VBA newbie, where do I put this in the VB Editor?

2) Where and when will it run? I am assuming upon opening the database?

3) If the references are not intact, how do I proceed?

4) Is this something that is recommended any time I create a shared database?

Thanks!
__1. You can place it in a Standard Code Module as a Public Sub-Procedure:
Expand|Select|Wrap|Line Numbers
  1. Public Sub AnalyzeReferences()
  2. Dim MyRef As Reference
  3.  
  4. For Each MyRef In Application.References
  5.   Debug.Print "Reference Name: " & MyRef.Name
  6.   Debug.Print "Is the Reference Built-In: " & IIf(MyRef.BuiltIn = True, "Yes", "No")
  7.   Debug.Print "Full Path of reference: " & MyRef.FullPath
  8.   Debug.Print "Version Number: " & MyRef.Major & "." & MyRef.Minor
  9.   Debug.Print "Kind of Reference: " & MyRef.Kind
  10.   Debug.Print "Is the Reference Broken?: " & IIf(MyRef.IsBroken = True, "Broken", "Intact")
  11.   Debug.Print vbCrLf
  12. Next MyRef
  13. End Sub
__2. It can be run anywhere in your Application at any time simply by calling it:
Expand|Select|Wrap|Line Numbers
  1. Call AnalyzeReferences
__3. From the Code Window ==> Tools ==> References. Find the missing Reference, it will be preceeded by MISSING:. Select the Reference ==> Browse ==> Navigate to the Folder indicated on the Full Path of Reference line on your Printout for the specific Reference ==> Open.
__4, It will not hurt to run this Procedure, but it is only recommended when you are experiencing potential Missing Reference(s) problem(s).
Mar 30 '07 #5

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

2 posts views Thread by Plex | last post: by
3 posts views Thread by Martin B | last post: by
7 posts views Thread by i | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by Gurmeet2796 | last post: by
reply views Thread by mdpf | last post: by
reply views Thread by harlem98 | last post: by
reply views Thread by listenups61195 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.