If you don't have something like Total Access Analyzer or Speed Ferret, then
you'll just have to do some good, old-fashioned debugging.
Follow the AutoExec, Startup Form, or other object and keep traceing until
you find where the culprit is.
Turn on the Macro Single step, use VBA breakpoints, etc...
"Guy" wrote:
> That is exactly what happened. What I don't know is where to look for the
> property that has the error in it. Any suggestions on that score?
>
> "S.Clark" wrote:
>
> > Create a new database file, then import everything from the current .mdb to
> > the new .mdb.
> >
> > If the problem doesn't go away, then it's possible that someone fat-fingered
> > a period into a property somewhere.
> >
> > "Guy" wrote:
> >
> > > I get this error every time I open ANY Access database.
> > > Can not find macro "."
> > >
> > > So does everyone else at my facility no mater what database is opened. It
> > > has to be something in the setup of Access but where do I look? We have both
> > > Access 2000 and Access 2003, both programs produce this error. Repair compact
> > > is not the answer, been there done that a million times. Re install does not
> > > help either.
> > > Repair installation does not help either.
|