Access 2007 hates Access 2003 macros

Rik_StHelens

Registered User.
Local time
Today, 22:41
Joined
Sep 15, 2009
Messages
164
Hi,

I've made a database on access 2003 because i hate access 2007. I've put it onto our company server, and on an individual C:\drive on 1 pc to see if it s a server security message but it isnt.

Every time i run a macro, whether it be to move records or generate reports i get the message "RunMacro Action Was Cancelled". I've tried SetWarnings and obvioulsy I have a stop macro command built in, but i cant get rid of this message. Its more annoying than anything to be honest.

Hope you can help

Thanks
 
Oh, and EACH USER needs to set that, it isn't a per database setting, but a per user setting.
 
Hi,

Thanks for the reply.

I have tried to add the location to the trust centre, however i get the error message "The remote or network path you have entered is not allowed under your current security settings"

I am trying a copy in My Documents, and one on a remote server.

Neither are working, do you have any ideas?
 
Hi,

Thanks for the reply.

I have tried to add the location to the trust centre, however i get the error message "The remote or network path you have entered is not allowed under your current security settings"

I am trying a copy in My Documents, and one on a remote server.

Neither are working, do you have any ideas?


I have managed to add it to trusted locations but I am still now getting the "Run Macro Action Cancelled" message
 
I'll have to check it when I get home (about 10 hours from now) as I don't have 2007 here at work. If anyone else with 2007 wants to try, feel free.
 
Hi

I have a further developments with the RunMacro Action was Cancelled prompt.

I have discovered that not all computers on our network display the message. I have set trusted locations on EVERY machine i have tested it on, and they seem to pick and choose as to whether they will display the message or not.

The file sits on a drive on our server, but if only certain machines display the message then i have no idea as to why.

hopefully someone can suggest something?
 
The file sits on a drive on our server...
Do you mean the database file sits on your server? If so, the database should be split (backend on server and copy of frontend on EACH user's machine). No database file should be opened by multiple people across a network. It is a guarantee for corruption.
 

Users who are viewing this thread

Back
Top Bottom