Macro enabled for everyone?

[bofonomo]

Hi,

I have a questionaire on a server, and I have managed to secure the database by hiding the navigation bars, password protecting the backend, and I have a macro that opens up a new blank form when the user opens the front end.

However when one opens the backend, the form displays the first entry of the database! Which defeats the privacy and security of the data!

How can I make it that the data base is macro-enabled for everyone?

Or is there another way round this, as in a prompt to enable the macro, or exit the database when you start?

Please, Any help would be great, it's really annoying me after so much hard work.

 

[Montez659]

I am not sure that I understand. You said the back end was password protected, so why is there a problem? Only people with the clearance to see all results would/should have access to the back end, i.e., with the password.

However when one opens the backend, the form displays the first entry of the database

Is this form automatically popping up because in the back end, there really shouldn't be any forms, just tables with the info.

Seems like something is off here. I will need more info.

 

[bofonomo]

Pardon me, that should read:

However when one opens the database, the form displays the first entry of the database,

 

[VBACO]

One solution I have used in the past is to set the database to open a "Enable Required" type form with a command button on it. Once Macros are enabled they can click the command button and move to the "new" blank form. I hope that makes sense to you.

 

[bofonomo]

Good idea, I will give that a go and let you know how it goes.

Thanks

 

[Montez659]

Do you have an AutoExec Macro that is opening the form? If so, why not set that to open a New Record?

 

[boblarson]

Do you have an AutoExec Macro that is opening the form? If so, why not set that to open a New Record?

If you do that then any macros that have actions that are considered unsafe by Access (the ones that appear when you click the SHOW ALL ACTIONS button on the Ribbon) won't run and neither will VBA. The user still needs to either enable macros/code or they need to set up the location of the frontend as a trusted location ON THEIR MACHINE.

You can do that by setting some registry entries or by letting them do it manually. The registry entries you need are shown here:
http://accessjunkie.com/faq_33.aspx

If you are using Access 2010, change the 12.0 to 14.0.

 

[Montez659]

Bob, I can understand that. I just can't figure out how he said it was opening to the first record of the db.

However when one opens the database, the form displays the first entry of the database

...and I have a macro that opens up a new blank form when the user opens the front end.

It seems like only one of these statements can be true, not both. If the db is in a trusted location, or if forced to choose to enable macros, the form would open to add a new record. If it wasn't a trusted location, and the disable option as chosen, the form shouldn't display at all since the macro that opens the form wouldn't be able to run.

Unless you are seeing something that I missed.

I mean, unless they meant that it is SUPPOSED to opening to a new blank record but it is not doing that.

 

[boblarson]

Bob, I can understand that. I just can't figure out how he said it was opening to the first record of the db.

First off - the thing to understand about Access 2007 and 2010 is that macros DO run. But macros that use actions that are considered "unsafe" do not run. A macro that opens a form is just a macro which opens a form. That is not considered an unsafe action by Access. So, it will run without enabling macros/code. The enabling of macros is just for those which may contain actions classified "unsafe," not all of them.

So, the macro can open the form and it would normally be displaying a record in it when opened. I don't know which actions are currently in the macro or if it is a different macro that supposedly sets the record to be a new record, but it sounds like there is enough of a disconnect that it will open the form at least.

 

[Montez659]

Ahh, ok. I guess I never thought that about that for some reason. Couldn't the problem be solved by using the Current Project IsTrusted criteria in the Macro for the form open command? Or better yet, just set the form type to Data Entry? This of course is merely a suggestion not knowing what other code is being performed.