I have a DB in Access 2003 which I want to deploy.
I've already applied all the necessary security settings.
I've also added a Form called frmInitialOpening which calls all the necessary
initialization procedures. This Form is set as the startupform of the DB
in order to be opened at the first opening.

The last procedure called by frmInitialOpening is the setStartUpForm,
which, as denoted by its name, sets the correct StartUpForm for the DB.

The problem is that due to some wrongly defined Permission,
the above procedure fails to set a StartUpForm.
My question is, which privilege is responsible for allowing such a change,
and in case it is something general like "Administer"
how to revoke it after setting the startupform.

No matter who opens the db you will still need to have the same startup form. simply go to tools > startup and nominate the start up form there.

No matter who opens the db you will still need to have the same startup form. simply go to tools > startup and nominate the start up form there.

I think you misunderstand my sayings.
Since this DB will be deployed I can't manually (from the menu) change the startupform, that's the reason I have to set it programmatically.

I emphasize the word change because as I wrote, I use a form (frmInitial)
only to run some initialization routines.
This Form is set as startupform in order to be opened at the first opening of the DB, and then after the initialization process is complete,
the startupform is changed to the standard frmMain of my DB.

Any other suggestions?

To do you initilization you could have an AutoExec Macro and leave the startup form as the form for users to see.

To do you initilization you could have an AutoExec Macro and leave the startup form as the form for users to see.

I thought that too, but the startupform option has precedence over the autoexec macro.
In other words if you have declared a startupform then you simply can not open any other Form before than that using the autoexec macro.