how to make an Access database multi-user?

[Nadinka]

Hi,
I have read many of the responses posted about multi-user Access database,
tried to follow the steps in creating a BE and FE, however, I am stuck in the
step that says that i should compile the FE mdb to an mde file. I tried to do
it and this message came: "You cannot create a Microsoft Access ADE or MDE
file from a database saved in Microsoft Office Access 2000 format. Convert
the database to the current version of Microsoft Office Access. Then create
the ADE or MDE file". Now what should I do?
Thank you in advance,
Nadinka

 

[Douglas J. Steele]

At the risk of sounding facetious, you should convert the database to the
current version of Microsoft Office Access.

Presumably you're using Access 2002 or Access 2003. Both of those versions
of Access use the Access 2000 file format (to increase interusability).
However, neither one can convert an application that's in Access 2000 file
format into an MDE.

Look under Tools | Database Utilities | Convert. If there's an option to
convert to a newer version, use it. Once you've done that, compile the
application (under the Debug menu in the VB Editor) to ensure everything's
okay. If it passes the compilation, then try to convert to an MDE.

 

[John Vinson]

Hi,
I have read many of the responses posted about multi-user Access database,
tried to follow the steps in creating a BE and FE, however, I am stuck in the
step that says that i should compile the FE mdb to an mde file. I tried to do
it and this message came: "You cannot create a Microsoft Access ADE or MDE
file from a database saved in Microsoft Office Access 2000 format. Convert
the database to the current version of Microsoft Office Access. Then create
the ADE or MDE file". Now what should I do?
Thank you in advance,
Nadinka

Well, perhaps you should do what the message quite clearly says:
convert the database to the current version of Microsoft Access.

Access 2002 and 2003 both default to creating databases in A2000
format - but cannot create a MDE file when the database is in that
format. Use Tools... Database Utilities... Convert to convert the
database to 2003 (or 2002, whichever you're using) format; you should
then be able to make it into a MDE.

John W. Vinson[MVP]

 

[David W. Fenton]

Look under Tools | Database Utilities | Convert. If there's an
option to convert to a newer version, use it. Once you've done
that, compile the application (under the Debug menu in the VB
Editor) to ensure everything's okay. If it passes the compilation,
then try to convert to an MDE.

I would always decompile and compact before recompiling, because
some invalid things that will prevent the creation of the MDE can be
marked as compiled and thus not be recompiled. The decompile
discards all compiling and insures that you're getting a 100%
compile on all the code.

 

[larrylinsonjr]

you could use Access Data Projects?

I just know that Aaron is going to reccomend it; I figured that we
should help Aaron out by getting the good word out.

-Larry

 

[Roger Carlson]

Very sad to use someone else's good name.

--
--Roger Carlson
MS Access MVP

 

[Nadinka]

Thank you very much Douglas for your response. Thank you to the other
responders too.
Now that i converted it to 2003 (which is the version that i have installed
in the computer), will this create a complication when i try to save the FE
in individual computers in the future?

 

[Nadinka]

I have Access 2003.

What version of Access are you using?

 

[Nadinka]

Thank you John for the reply.

Well, perhaps you should do what the message quite clearly says:
convert the database to the current version of Microsoft Access.

Access 2002 and 2003 both default to creating databases in A2000
format - but cannot create a MDE file when the database is in that
format. Use Tools... Database Utilities... Convert to convert the
database to 2003 (or 2002, whichever you're using) format; you should
then be able to make it into a MDE.

John W. Vinson[MVP]

 

[Tony Toews]

you could use Access Data Projects?

I just know that Aaron is going to reccomend it; I figured that we
should help Aaron out by getting the good word out.

-Larry

This posting was not by Larry Linson and is a forgery.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Douglas J. Steele]

It'll only cause a problem if your users don't have Access 2003.

 

[Douglas J. Steele]

I would always decompile and compact before recompiling, because
some invalid things that will prevent the creation of the MDE can be
marked as compiled and thus not be recompiled. The decompile
discards all compiling and insures that you're getting a 100%
compile on all the code.

Even though MichKa says you should use /decompile sparingly?

 

[David W. Fenton]

Even though MichKa says you should use /decompile sparingly?

I have used it daily in A97 and A2K and have never lost any code or
any other objects. I very rarely encounter any code corruption at
all, and I believe it's because I have conditional compiling turned
OFF and because I decompile frequently. With A97, I usually
decompile at the end of each day's programming work, with A2K, just
before distributing a new update. So, I do decompile less frequently
in A2K than A97, but I still do it as a regular part of my
development practices.

The point is, if you keep your compiled code clean, it has less
chance to develop problems. If you never decompile, your compiled
code can be an incredible mess, and then you can lose things.