Acc2003 Object Name Reference Problems!!!

W

WW

Well, I upgraded everything from Office 2000 to Office
2003. Now I have a major problem. Access 2000 never cared
if you refer to an object as
-----------------------
[Forms]![frmExplorer]![sbfrmGeneric]![cbo_Search]
-----------------------

or as

-----------------------
[Forms]![frmExplorer]![sbfrmGeneric].[Form]![cbo_Search]
-----------------------

but Access 2003 (with 2002-2003 file format) does - and
now my 60 Mb front-end application has forms w/ subforms
that no longer function because of this. The amount of
code that I would have to sift through to fix this is
enormous. Queries, forms, subforms, reports, and modules
could all have these inadequate references. If no one has
a solution - I will have to go back to Access 2000.

Thanks for any advice.
-WW
 
M

M.L. Sco Scofield

I had a similar problem. In my case I solved it by reducing the security setting (Tools/Macro/Security...) to "Low."

Although a little dangerous, this did get me by my problem temporally until I can learn more about the whole certificate thing.

And to put dangerous into perspective. Setting it to low makes it just like Access 2000 and 2002 which didn't have any VBA security.

To aid with making global changes which you might end up having to do in the future, my favorite product is "Find and Replace" from
Rick Fisher Consulting at http://www.rickworld.com.

Good luck.

--

Sco

M.L. "Sco" Scofield, MCSD, MCP, MSS, Access MVP, A+
Useful Metric Conversion #16 of 19: 2 monograms = 1 diagram
Miscellaneous Access and VB "stuff" at www.ScoBiz.com
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top