Starup Options

[Marko via AccessMonster.com]

Hi all,

I have set my Access DB to startup with a form and disable full menu, built-
in tool bar ... the only thing allowed is the special key to display the
database windows. I forgot to save a copy before I made the changes and now I
need to change the startup form, is there a way to reset these setting back
to default?

Thanks

Marko

 

[Dirk Goldgar]

Hi all,

I have set my Access DB to startup with a form and disable full menu,
built-
in tool bar ... the only thing allowed is the special key to display the
database windows. I forgot to save a copy before I made the changes and
now I
need to change the startup form, is there a way to reset these setting
back
to default?

That depends on how thoroughly you disabled things. Try holding down the
Shift key while you open the database, and see if you get access to the full
menus again.

 

[Marko via AccessMonster.com]

Thanks Dirk! It worked perfectly. By the way, is there anyway to totally
disable other people from modify the data table and the design? I only want
to let the users do Data Entries and Run Reports base on the predefine
specifications and designs. That's why I specified startupform and disble all
these menu to hide the database windows so user can only use what ara
available on the startup form to perform their jobs.

Best regard,
Marko

Hi all,

[quoted text clipped - 6 lines]

back
to default?

That depends on how thoroughly you disabled things. Try holding down the
Shift key while you open the database, and see if you get access to the full
menus again.

 

[Dirk Goldgar]

Thanks Dirk! It worked perfectly. By the way, is there anyway to totally
disable other people from modify the data table and the design? I only
want
to let the users do Data Entries and Run Reports base on the predefine
specifications and designs. That's why I specified startupform and disble
all
these menu to hide the database windows so user can only use what ara
available on the startup form to perform their jobs.

You can prevent them from using the Shift key trick by setting the
AllowBypassKey option to No -- you'll have to search the web or newsgroups
for that, as I can't recall the details offhand.

You can distribute your application as an MDE (Access 2003 or earlier) or
ACCDE (Access 2007). That strips out all source code and disables the
design view of all forms and reports (maybe macros, too; I can't recall).

People could still get to your tables, if only by linking to them from
another application, unless you decide to implement user-level security and
remove design permissions from the Users group. That can be cracked, but it
will keep out anyone who isn't reall determined. However, it's tricky to
get user-level security set up correctly, so it's not something you should
undertake without studying it thoroughly first.

And remember, the more you lock things away from the users, the more you
lock them away from yourself if you lose the keys.

 

[Jason]

MDE would be the best way to go. I had code to enable and disable these
types of lock outs depending on external criteria. The problem now is that
when I copied the mdb file to another computer and back again the code fails
due to vba error!

 

[Marko via AccessMonster.com]

Thanks Jason and Dirk!

I'll look into the MDE options. Also, where can I find more information on
MDE? I wuold like to be throughly about MDE before I make the changes.

Many thanks
Marko

MDE would be the best way to go. I had code to enable and disable these
types of lock outs depending on external criteria. The problem now is that
when I copied the mdb file to another computer and back again the code fails
due to vba error![quoted text clipped - 22 lines]

And remember, the more you lock things away from the users, the more you
lock them away from yourself if you lose the keys.

 

[Marko via AccessMonster.com]

Thanks Jason and Dirk!

I'll look into the MDE options. Also, where can I find more information on
MDE? I wuold like to be throughly about MDE before I make the changes.

Many thanks
Marko

MDE would be the best way to go. I had code to enable and disable these
types of lock outs depending on external criteria. The problem now is that
when I copied the mdb file to another computer and back again the code fails
due to vba error![quoted text clipped - 22 lines]

And remember, the more you lock things away from the users, the more you
lock them away from yourself if you lose the keys.

 

[Dirk Goldgar]

Thanks Jason and Dirk!

I'll look into the MDE options. Also, where can I find more information on
MDE? I wuold like to be throughly about MDE before I make the changes.

The first place to look is in the help file. I don't believe you've said
what version of Access you're using, but if you open help and enter "MDE" in
the search box, you should find topics on the subject. In Access 2003, the
top topic I was "About MDE and ADE files", and clicking that got me to a
topic where I could choose "About MDE files (MDB)" , and that got me to a
topic showing lots of information.