Recent content by Morphius

Very interesting...I'll explore this area more and let you know how it goes. Having said that, I wish to thank everyone who contributed to this thread. All of you made is so much easier for me to locate the answers I needed. It's been very much appreciated. Thank You All.

Right, but the runtime's don't come with any design capabilities either so runtime users would obviously not be a concern. The concern is regarding users with or access to full A2007 and using it pirate the design.

Okay so here's what I did and it seems to have worked... 1) Ran the Debug/Compile on the VBA coding (found an extra "end if" that didn't belong to anything) 2) Clicked on the "Office" button 3) Went to Access Options 4) Clicked on Navigation Options and unchecked Tables, Queries, Forms...

This is the message I get when I attempt to make the front-end into an ACCDE format... "Microsoft Office Access was unable to create the .accde file" "This error is usually associated with compiling a large database into an MDE file. Because of the method used to compile the database, a...

Right...which all the databases are already separated into front-ends and back-ends. The front-end is used by many people however and the back-end is kept on a network drive. The back-end is just the tables...which I'm not worried about the table data since the concern is the pirating of the...

Wow never thought of opening a database in Notepad before now...tried it and while there was a lot of garbage data, I was still able to find the module commands so I now know what you mean. So then is there a way to prevent users from using a blank database to import the macros, modules and...

Could we set a password for the database which the autoexec (onload form) handles? If so, the user would never see the password governing the database unless they tried to import part of the database into another on their own..!?

VERY VERY COOL. But I am able to use another Access database to essentially copy the form and look at the design view side...thus allowing me to bypass the setup..which is the very thing I want to prevent.

I'm not so much concerned with table data as I am with the queries, macros, modules and forms. The tables really only contain data entry but the rest contain operational related coding and/or settings that could be used to recreate the databases.

Access 2007

My new CIO has decided that he wants everything locked down with all our Access databases. He wants to ensure that no user can: a) see the Access Objects pane. (so cannot see tables, queries, modules, macros) b) cannot access Design View. c) cannot right-click. d) cannot use Shift at the...