MS Access 2003-missing or broken reference to the file "mscomct2.o

[Just Me]

MS Access 2003 w/Windows XP Professional

We have a small Access database on a small server accessed through 8 work
stations. 6 can access and utilize the database succesfully. We recently
purchased setup 2 new PC's with MS Access 2003 w/Windows XP Professional (the
same as the other workstations). Whne we try to open the database from eithe
of the new PC's, we get an error message that "the database or project
contains a missing or broken reference to the file "mscomct2.ocx" veriosn
2.0". We can click the OK button and continue opening the database file.

Why is this happening? Do we have to do something to "link" the workstation
verison of Access 2003 to the database on the server? Should I be worried
about the integrity of the database if I allow a user to work in the database
from those two workstations?

Any ideas, suggestions, comments?

 

[kc-mass]

The file "MSCOMCT2.OCX" has to be installed on the new machines and
registered.

It may be that you have the file but it is not registered. It should be in
the Windows\System32 directory.

If you find it and just need to register it, note its location, then from
the start menu, RUN CMD.
You'll be given a DOS like interface. change to the directory where it is
located and run
"Regsvr32 MSCOMCT2.OCX"
It should come back with a message saying "DllRegisterServer ... succeeded"

If the file is not on your new systems, it is on the 6 working PCs just copy
it off one of those.

Regards

Kevin

 

[Just Me]

Ok...I copied the MSCOMCT2.OCX file from another PC into the Windows\System32
directory on the new PC...Now I am trying to register it...I went to
Start>Run and then what? Do I type in RUN CMD

 

[Just Me]

THANK YOU!!!! I DID IT!!!!

The file "MSCOMCT2.OCX" has to be installed on the new machines and
registered.

It may be that you have the file but it is not registered. It should be in
the Windows\System32 directory.

If you find it and just need to register it, note its location, then from
the start menu, RUN CMD.
You'll be given a DOS like interface. change to the directory where it is
located and run
"Regsvr32 MSCOMCT2.OCX"
It should come back with a message saying "DllRegisterServer ... succeeded"

If the file is not on your new systems, it is on the 6 working PCs just copy
it off one of those.

Regards

Kevin

 

[Tony Toews [MVP]]

We have a small Access database on a small server accessed through 8 work
stations. 6 can access and utilize the database succesfully. We recently
purchased setup 2 new PC's with MS Access 2003 w/Windows XP Professional (the
same as the other workstations). Whne we try to open the database from eithe
of the new PC's, we get an error message that "the database or project
contains a missing or broken reference to the file "mscomct2.ocx" veriosn
2.0". We can click the OK button and continue opening the database file.

1) Do you need that control? mscomctl2.ocx sounds like it's for
serial port communications?

2) The problem may very well be that kill bits were set on slightly
older versions of those OCXs. However if so that puzzles me why you
didn't get the problem on your six PCs.

An older version of MSCOMM32.OCX has had the "kill bit" flag set.
http://msmvps.com/blogs/access/arch...-has-had-the-quot-kill-bit-quot-flag-set.aspx

3) Alternatively to the control we've had good reports on using API
calls directly. See the Serial Port Communications page at my web
site. http://www.granite.ab.ca/access/serialport.htm

Do we have to do something to "link" the workstation
verison of Access 2003 to the database on the server?

No, problems with OCXs are always on the client PC and not the server.

Should I be worried
about the integrity of the database if I allow a user to work in the database
from those two workstations?

No.

Tony

 

[kc-mass]

Hi Tony,

I believe that that OCX works with the Office calendar/Date picker that
unfortunately many Access applications use.

Regards

Kevin

 

[Tony Toews [MVP]]

I believe that that OCX works with the Office calendar/Date picker that
unfortunately many Access applications use.

You could be quite right about that. And
http://support.microsoft.com/kb/297381 confirms that.

In which case dump the control. See the Calendar Tips page at my
website
http://www.granite.ab.ca/access/calendars.htm

There could, likely will, be lots of version problems when you go to
distribute the MSCal.OCX..

One alternative is MonthCalendar is a completely API generated Month
Calendar derived directly from the Common Control DLL. There are
links to several downloadable calendar forms at my website. As these
are forms you can also do anything with them you want.

You can also use the calendar form which comes in the Access <insert
your version here> Developers Handbook by Litwin/Getz/Gilbert,
publisher Sybex www.developershandbook.com. These books are well
worth spending money. Every time I open one I save the price of the
book.

Duane Hookum has an awesome and simple calendar in a report. See the
Calendar Reports sample section at
http://www.access.hookom.net/Samples.htm

Tony