Installed updates, now macros don't work!

microsoft.public.access.security

10 Jul 2006 4:41 PM

Nik

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,

10 Jul 2006 5:29 PM

'69 Camaro

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.

Show quoteHide quote

"Nik" <N**@discussions.microsoft.com> wrote in message
news:3FF3B113-1269-401D-8B2E-3FD2DED2A577@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,
>

10 Jul 2006 6:24 PM

Nik

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

Show quoteHide quote

"'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" <N**@discussions.microsoft.com> wrote in message
> news:3FF3B113-1269-401D-8B2E-3FD2DED2A577@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,
> >
>
>
>

10 Jul 2006 8:26 PM

Nik

When I go into the script editor on the problem computer, it obviously
provides an error when I run the macro. But when I do the same thing on a
Windows XP/Access 2003 computer, I don't receive any errors at all. I'm not
sure I want to just change something on one computer, do I? Is this still
the best way to do it, even though nothing's changed in the database since
well before I applied the updates?

Thanks,
Nik

Show quoteHide quote

"Nik" wrote:

> 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" <N**@discussions.microsoft.com> wrote in message
> > news:3FF3B113-1269-401D-8B2E-3FD2DED2A577@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,
> > >
> >
> >
> >

10 Jul 2006 8:42 PM

'69 Camaro

Hi, Nik.

> When I go into the script editor on the problem computer, it obviously
> provides an error when I run the macro.

What error message is the VB Editor giving you? "Data member not found"? I
probably should have asked you to compile the code before attempting to step
through the code execution.

> I'm not
> sure I want to just change something on one computer, do I?

Depends upon what the problem is. If it's a compile error due to a missing
reference, then adding that reference to this file and recompiling is
usually acceptable. Deleting database objects is not.

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.

Show quoteHide quote

"Nik" <N**@discussions.microsoft.com> wrote in message
news:3B5735AA-2729-4E8C-B1AA-5BC0AABFDE3B@microsoft.com...
> When I go into the script editor on the problem computer, it obviously
> provides an error when I run the macro. But when I do the same thing on a
> Windows XP/Access 2003 computer, I don't receive any errors at all. I'm
> not
> sure I want to just change something on one computer, do I? Is this still
> the best way to do it, even though nothing's changed in the database since
> well before I applied the updates?
>
> Thanks,
> Nik
>
> "Nik" wrote:
>
>> 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" <N**@discussions.microsoft.com> wrote in message
>> > news:3FF3B113-1269-401D-8B2E-3FD2DED2A577@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,
>> > >
>> >
>> >
>> >