Help with Access 2007 Developer Runtime

[TheTomCat]

I have recently converted over to Access 2007. I package my application using the Packaging Wizard. When a user installs, it apparently only lets the user open the application in Runtime version. This is actually a Good thing.

Question: Is there anyway for a user to get around the runtime if they have Full Access 2007 on their machine?

I have tried and I cannot. You cannot change the extension, Shift ByPass will not work, etc.

I guess the only way a developer would get around it would be to redesign the Master, then overwrite the user's Front End, then relink to the Back End.



Thomas Bailey
a/k/a TomCat

 

[jrbarnett]

Have you tried manually opening the installed application using a full copy of access 2007 (whether or not the runtime is installed) ? If it doesn't let you, then its an interesting development.

This would seem to me to be the easiest way of getting around the runtime limitations.

John

 

[TheTomCat]

Yes I have tried it with Full Access and it will still only open in Runtime.
Now, this is because I chose it that way in the packaging process. You could choose another option and probably open in Full Access but I chose the third option (Access 2007 Packaging Wizard).

I was just wondering, since I chose this option, does anyone know of anyway to get around the runtime? I hope there is NOT anyway. I want a extra layer of protection.

Thanks.

Thomas Bailey
a/k/a TomCat

 

[jrbarnett]

What about on a PC without runtime access 2007 installed?

John

 

[TheTomCat]

Now that I haven't tried. The machine has both Full Access and 2007 Runtime on it.
I will find a machine to try it on W/O Runtime and Post back.

Thnaks.

Thomas Bailey
a/k/a TomCat

 

[cmohr]

The packaging wizard is simply that. It creates a runtime package that stands by itself and keeps the end user from changing anything other than the data that your application allows them to access. It’s a nice, safe, clean way to give an end user your final product.
If you want to give your database as a runtime and also keep it useable in access, give the user your front end database, but rename the extension to .accdr to make it a runtime version and instruct anyone who may need to open it in access to rename it back to .accdb. WARNING: this opens the database up to modifications. That’s why it’s a good idea to package it instead. It’s safe that way. If the user doesn’t know about the extension name change and they have runtime installed, the .accdr will open just like it would if you packaged it for runtime, without having to run the install process. But if they know that they can rename it, it won't be secure.
You can try this on your computer with access installed. If you open the .accdr database, it will look like you opened it in runtime.