Through the tools->Startup menu I have declared that a database opens with a specific form and that most bars do not show, however now I cannot reverse this so that I can edit the forms, is there something I can do? I can't seem to find an option to change the startup options

also since the users of this database will probably be able to screw up everything because they don't pay that much attention, is there a way to lock the database so that they can only edit it through the forms and so that they cannot modify the forms/queries/reports without some sort of password?

finally is there a way so that alt-enter can be set to not showing properties? on the former program they used alt-enter was used to change between languages and I'm afraid there will be a lot of accidental property changes

DrCruces,

Not something I have a great deal of experience on, but try opening with SHIFT held down, this bypasses the autoexec function and any OnStart actions, but you may have disabled this in the properties too!

To make the db nonUser changeable, you could investigate making your development an .mde, this has its own drawbacks though. Or you could use the Access security features, I wouldnt advise it though!

I personally suggest looking at all the options available to you, there are books out there just for this part of development in Access, not sure if Wrox do, the book I have on it is, err, not Wrox (sorry!). No single method wins over any other, in my opinion, they all have their own usefulness and problems.

Meanwhile, if SHIFT offers no hope, hopefully someone else here can let you in to your development!

Lee

DrCruces,
You can get all your objects in your database back and be able to make changes, but you will need to start a new database then import everything into your new database. This will give you an identical copy of your database, but without any startup options.

For your security, Lee was right...there are options, but all have draw backs. My preference, is creating all the security in VBA and form design, then making an .mde file to push our to the end users. The draw backs with this is that all code and design is frozen and not able to be changed, so you will have to keep a copy of the database without startup options set to make any changes to if need be. This is also a plus though, because no one can get behind the scenes of your database. Then you would have to create an .mde file after any changes and re-issue it to your users. This seems like a pain, but it is the method that works the best for me in a company with locations around the world and moving across a network with 200+ users.

Hope this helps!

Regards,
Laura

The only thing standing between you and your goal is doubt. Quit doubting yourself and you'll be able to accomplish anything!

Thank you both

shift indeed allowed me to open the database without the startup thing, also that mde option you mentioned seems promising, I'm already searching on how to change my database to an mde, thanks a lot again

it seems I can't change my database to an mde, it says that the conversion generates a large number of tableids (though my database uses one table with 12 columns, 12 queries 5 forms and 2 reports), any idea what I did wrong or any other solution, I tried the security option but it doesn't seem to be doing any good since by default access gives whoever opens access administrator rights to everything (go figure)

You should be able to configure the security to what you want, it is a pain in the ass though, and I tend not to use it.

That said, I cannot see why it wont produce an mde for you.