> Well I don't think there's anything actually wrong with the code because it
> works fine in Access 2003 on other machines. But I am stepping through it
> now.
> Nik
>
> "'69 Camaro" wrote:
>
> > Hi, Nik.
> >
> > > How can I either roll back the updates I installed or modify a setting to
> > > allow that macro to run?
> >
> > Why not just fix the problem that is causing the macro to fail to execute?
> > Find the Startup( ) function in a VBA code module (press <ALT><F11> to open
> > the VB Editor, and then use the binoculars "search" in the menu) and set a
> > breakpoint on the first line of this function, then execute the Autoexec
> > macro so that you step through each line of the Startup( ) function.
> >
> > HTH.
> > Gunny
> >
> > See
http://www.QBuilt.com for all your database needs.
> > See
http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
> >
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
> > info.
> >
> >
> > "Nik" <Nik[ at ]discussions.microsoft.com> wrote in message
> > news:3FF3B113-1269-401D-8B2E-3FD2DED2A577[ at ]microsoft.com...
> > >I have a Windows 2000 server that holds an Access 2002 database. Users
> > >used
> > > to be able to open this database through Terminal Services when necessary,
> > > but every since I installed Windows and Office updates toward the end of
> > > June, the database gives the following error when opened:
> > >
> > > Action Failed
> > > Macro Name: AutoExec
> > > Condition: True
> > > Action Name: RunCode
> > > Arguments: Startup ()
> > >
> > > And the only action I can take is to Halt. Then the database does not
> > > work.
> > > How can I either roll back the updates I installed or modify a setting to
> > > allow that macro to run? I thought that in the Tools > Macro menu there
> > > was
> > > a Security option, but there isn't one.
> > > Thanks,
> > >
> >
> >
> >