1. In your response you indicate that need to "find the original MDB
front-end". I was used to referring to the MDE as the front-end and the
MDB as the back-end. To be clear, what is the MDB front-end you are
referring to or was this a typo?
The mdb front end is of course the original mdb you had to make the mde. As
a
developer, you work on the mdb, you need the mdb, and only RIGHT before you
deploy to your users do you convert the mdb to a mde. This generally makes
the mde a bit smaller. The only requirements you need to make a mde is that
ms-access is the in the SAME VERSION as what you are developing under. All
versions of ms-access include the ability to make a mde. The resulting mde
does result in a smaller file. It does not result in some windows package,or
result in a multiple disk set as you mention. You simply go convert to mde,
and you get a slight smaller mde file. It is a quick and easy process.
2. To convert the original MDB, do I have to correct the references in
Access97 first, then copy that MDB to my Access 2002 & convert? Or,
can I correct the references in Access2002, then convert --leaving
Access97 out of the picture?
You should try and remove un-necessary refs. As the other poster mentioned,
it seems you don' likely need that ref in a97. As a general rule, a2003 will
covert, and fix/change the refs for you. If your a97 mdb file compiles
correctly, then it should convert without problems.
After you got the a2003 database. You need to test it, compile the code,
and ensure no errors. Again, as a general rule, my a97 applications convert
without any problems to a2003. You should then have no problem
making a mde.
Regardless, BEFORE you try and make a mde, you need to compile the code
in a2003, and remove all errors. (ctrl-g...in the code window, you go
debug->compile).
3. How do I get my customer's data into the "new" version? I would
assume, after converting the MDB, I can import their tables, then make
the MDE??
Just open the data part with a2003, and it will ask you to convert. Convert,
and you are done.
The code part (front end) is the one where you need ensure that the code has
no errors, and you can compile the code. Only AFTER you get the code to
compile, do you then attempt to make a mde...
4. My customer is using Access 2003 - I am limited to Access 2002. Is
there going to be a problem?
a2003, and a2002 actually "default" to a2000 format. However, that is
generally ok for data, you are talking developers, developing code, and
working on a application. So, this process brings in a new dimension. Since
a2002, and a2003 share the same format, then you can do this work on your
a2002 machine.
However, right before deploying, I would use a2003 to make the mde
5. How do I reinstall the program onto my customer's computer - I
assume a CD is generated when I make the MDE? I used 9 floppies
before...
No, a mde file is created by going tools->database utile. The result is a
mde file. There is no cd, or nothing generated here.
Try making a simple form with "hello" on it..and then make a mde out of
this mdb.
To install the mde application on the target computer, you need to have
ms-access installed on that computer. You can also consider using the
developers edition of ms-access, and this does allow you to create a windows
package that includes your mde, and a ms-access runtime. However, the
process of making a mde is not really related to the process of creating a
package with the developers tools for office (which you likely don't have).
So, it is not clear if the target computers already will have ms-access
purchased and licensed or not. If they are NOT going to purchase ms-access
for each machine (ie: users don't really use ms-access, but *just* a
application created with access), then you will need the developers tools,
and that allows you to build and create a runtime. If they already got
ms-access, then you don't need to "package" anything. I often build a batch
file, or use
www.winzip.com to zip up the contents, and give that to each
user. I used a registered version of winzip for a long time now. You don't
need winzip, and can just email, or give each user a copy of this mde file.
There is no "install" required. However, I use winzip, and no Inno so that
users don't have to be "told" where you save the file. Also, a installer can
build shortcuts on the desktop etc for you. But, you don't need a installer
to deply a mde to a machine with ms-access already on it.
The concepts, and as "why" you split are explained in detail here:
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
I also mention the issue of making a mde in the above...
