Making An MDE

[DS]

So I'm almost ready to wrap this up and I'm wondering about the process.
Is this right?

1 Change db file format from 2000 to 2003
2 Compile
3 Splt
4 Make MDE of Front End
5 Use Access 2007 Runtime to make a distributable application.

1 Install MDE Front Ends on Workstations
2 Install Back-End and Front End on Server

3 It's Done

DS

 

[Golfinray]

Depends on how much security you want. Try reading Joan Wilds site on
security and database splitting at www.jmwild.com Also, google Albert
Kallal, he has an excellent site with splitting instructions.

 

[Klatuu]

I don't think you will be able to create an accde (2007 equivilant to mde)
from a 2003 mdb. I haven't tried it, but historically, the file has to be in
the current version format before you can create an mde (accde) or run it
using the runtime.

For example, I don't know if a 2003 mdb would even run using 2007 runtime.

 

[Chris O'C via AccessMonster.com]

He plans on creating the 2003 mde in 2003 but deploying the app with the 2007
runtime, which is possible. That plan requires good error handling, a
startup form, and testing in the retail version of Access 2007 because the
custom menus or custom ribbons he has to build (if he needs *any* menus or
ribbons, since the runtime doesn't show the built in ribbon) won't look the
same in 2007.

Chris
Microsoft MVP

 

[Klatuu]

Have you actually done this?
What I am saying is I doubt an mde or mdb will run on 2007 runtime.
I know you can using 2007 full install, but I doubt it would work using the
runtime. It might, but I haven't tested it.

I would agree; however, that it would require testing with a full install of
2007 first, but then if you have 2007, why not convert to 2007 and then
deliver the run time.

 

[Chris O'C via AccessMonster.com]

I've tested both Access 2000 and 2003 with the 2007 runtime. They work. I'm
guessing he doesn't have Access 2007 retail. He's just hoping 2003 will work
in the 2007 runtime without modifications. Wishful thinking.

Chris
Microsoft MVP

 

[Klatuu]

That is what I expected. 2007 runtime and dev tools are certainly a lot less
expensive the 2003

 

[DS]

Ok, I 've read all of the post and I'm replying to all via the last one just
to simplfy the matter. I developed the app in Acess XP 2002 wih a file
format of 2000. I own 2007 but not 2003. I'm just trying to get this app
runtime so that the end user doesn't need access on their computer. (Do
they still need runtime though?) This is all nearly confusing but I'm
sure with your help I will previal. So with all of this background info,
what is the best way to end up with an app that doesn't require Access. PS.
I have no menu bars, title bars, ribbons or whatever there are. Thank you
for your help. it is much appreciated.
Thanks
DS

 

[Klatuu]

Convert the app to 2007
work out the bugs
download the free 2007 runtime and developers extensions.

For any Access application, a minimum of the runtime version is required.
When you create an install package with the developers extensions, you will
be able to include the runtime in the package you deliver to the users.

 

[John W. Vinson]

Ok, I 've read all of the post and I'm replying to all via the last one just
to simplfy the matter. I developed the app in Acess XP 2002 wih a file
format of 2000. I own 2007 but not 2003. I'm just trying to get this app
runtime so that the end user doesn't need access on their computer. (Do
they still need runtime though?) This is all nearly confusing but I'm
sure with your help I will previal. So with all of this background info,
what is the best way to end up with an app that doesn't require Access. PS.
I have no menu bars, title bars, ribbons or whatever there are. Thank you
for your help. it is much appreciated.
Thanks
DS

Just to amplify on what Dave is saying:

You have two choices. You can pay a fair bit to purchase the Access
Developer's edition for A2002: see

http://www.granite.ab.ca/access/developereditionversions.htm

for the various options. This will let you create a Runtime version of
Access... which your user MUST install on their PC in order to use your
database. (It is not possible to run an Access database without some version
of Access on the computer, either purchased or runtime).

Or, you can install 2007, and use the free 2007 runtime version.

In either case, the user needs some version of Access - either the full
version (the same or a later version of Access than you used to develop), or a
runtime version. Once they have that, they can open and use your .mdb or .mde
file.

 

[DS]

Thanks John.
I have it now!
DS

 

[DS]

Thanks Dave...
I'm on my way now!
DS

 

[Chris O'C via AccessMonster.com]

Just to clarify, in the future you'll be able to make mdes in Access 2002
format, Access 2007 format and accdes in Access 2007 format, but not Access
2K or Access 2003 mdes, because you don't have those other versions installed.


Chris
Microsoft MVP

 

[DS]

So even though I'm developing in file format 2000 using Access 2002 I won't
be able to make an mde in 2000 file format? At this point I suppose 2000,
2002 are many moons ago and I should probably look towards the future.
Thanks
DS

 

[Chris O'C via AccessMonster.com]

Sorry, you need Access 2K to make Access 2K format mdes. For compatibility,
it's best to work in and make an mde in the lowest format your users will be
using. If you have Access 2002 customers, then make Access 2002 mdes.

Chris
Microsoft MVP