Run Time Error

[PureEvil]

I have a report form for entering parameters to produce a report. This
report ran fine before my computer had a meltdown - I've since put in a new
harddrive, motherboard and power supply, loaded everything and I am using a
backup copy of the database.

The database is split. It works fine on another machine. Someone has
suggested "missing libraries".

On my machine I get a "run-time error 2683. There is no control in this
object". When I click debug the debugger takes me to the FromDate section of
the code - which is displaying as 1/1/2005. If I close the debugger, the
form opens and I can select parameters from every spot except the From Date
and To Date sections.

Running XP Pro
Office 2003
All updates have been installed.

Suggestions anyone?

Pamala

 

[Allen Browne]

There could be several things happening here, but the sequence below should
deal with most possibilities, Pamala.

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
and the code syntax is compilable.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

 

[PureEvil]

Hi, thank you for the information. I followed all the steps and none worked.
I'm being told that I am missing files from c:\windows\system32 - namely 4
files that should be with mscomctl.ocx aren't there so I don't have the
necessary files for the dtpicker. However, the person giving me this
information can't tell me how to get these missing files loaded.

It occurred to me that I loaded Access 2003 previous to the melt-down on a
machine that had 97 and 2000 Access installed. So, I uninstalled Access
2003, reinstalled Access 97, Access 2000 (upgrade), did the updates for 2000
then reinstalled Access 2003. (I think this goes without saying, but just in
case, yes, all three disks are original, legitimate Office disks).

At this point, I'm still getting the error and don't know where to go to get
the missing files. The missing control seems to be the dtpicker. My install
of Access doesn't have one. But, it did before the meltdown because
everything did as it was supposed to.

I've encountered several sites on the internet promising they can "fix"
mscomctl.ocx etc, but I don't recognize any of them and don't know if they
can be trusted. I also found this site
http://support.microsoft.com/?kbid=896559, but while it's talking about the
same file, it's talking about a different error message.

I'm at my wits end here. Any other suggestions?

I appreciate your help with this.

Pamala

 

[Allen Browne]

Open a code window.
Choose References on the Tools menu.
You will find that one (or more) of the files are marked "MISSING".
That's the cause of the problem.

The solution might be to search the hard disk to find the appropriate file
(or even copy it from another machine). Once found use regsvr32 to register
it. There's more details about that in:
Solving Problems with Library References
at:
http://allenbrowne.com/ser-38.html

Note that you have to have not only the file, but also the right version. As
your research confirmed, this is a bit of a nightmare to maintain over time,
on different machines, with different versions of Access and even different
versions of Windows. The better solution is therefore to simply avoid these
ActiveX controls and OCXs, and save yourself the bother. You can use a
simple little Access form as a popup calendar instead of the date/time
picker (which also has other problems such as handling Null.)

You can download such an Access form from lots of places on the 'net. Here's
one:
Popup calendar
at:
http://allenbrowne.com/ser-51.html