By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,238 Members | 1,459 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,238 IT Pros & Developers. It's quick & easy.

Missing .OCX files after 2003 upgrade

P: n/a
Hi ;

I just upgraded to Access 2003 from 2000. I'm not real happy about it
right now, even though I do see MS added some stuff that I wish they
had in 2000.

I tried to open my db and first of all got the sandbox message. I set
the security level to low on macros, and that problem went away (at
least for a little while). My real problem is that when I deploy the
database and install the runtime, I get a message like this, "Your
database or project contains a missing or broken reference to the file
'MSINET.OCX' version 1.0". I get the same message for the files named
COMDLG32.OCX and COMCTL32.OCX. Even then, the program will run until I
open a certain form, then boom. There's a ton of VBA associated with
this form, so tracking down the offending code would be a pain. Is
there an easier way? And why would I get a message like this in the
runtime when I don't get any errors at all while running the program
within Access?

Also, I get the "sandbox" security message in the runtime. Is there
any way to turn it off?

G. Miller

P.S. - I don't have any "MISSING" references. Unfortunately, I had two
after the upgrade and can't remember which two they were.
Nov 13 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.