What version should my database be

[James Ivey]

Access Newbie here.

I've got Access 2003 (11.6355.6360) SP1

At the top of my database window, it says:
DatabaseName : Database (Access 2000 file format)

Under the Tools menu, I've got:
Tools>Database Utilities>Convert Database
and one of the options is "Convert to Access 97 file format",
and the other option is to "Convert to Access 2003-2003 format"

Why does Access 2003 create a file in 2000 format?

Should I convert to 2002-2003 format?

Thanks for any insight.

James

 

[tina]

the answer depends on a number of things, and it may change from database to
database. for instance: who will be using the database? if there are
potential users who only have A2000 available, then you'd want to create the
db in (or convert it to) A2000 so it could be used by A2000, A2002 and A2003
users. and there are a few issues to be aware of when you build an A2000 db
using A2003 software; some program enhancements that were introduced in
A2003 will be available in the A2000 db as you're building - but they will
NOT work when you work in the db *using A2000 software*. (i got bit by that
one myself, just a couple days ago!) do you need to use certain program
enhancements that were introduced in A2002 or A2003? if so, and if there
will be no A2000 users, then you'll probably want to create the db in
A2002/A2003 format rather than A2000 format. also, you can create an A2000
db using A2003 software, but you *cannot* convert that db to a .mde file
using A2003 - to do that, you need the A2000 software.

note that while the default file format is A2000, in the A2003 program, you
can change the default file format from the database window's menu bar -
Tools | Options | Advanced tab | Default File Format setting on the upper
right side of the tab page. changing this setting does *not* affect the open
database, or any other existing database that you open. it only controls the
file format used to *create a new db*. and whatever file format you create
the db in, you can always convert it to another version later if you choose.

hth

 

[James Ivey]

Thank you very much Tina. I appreciate your reply.

I'm only going to have 3, maybe 4 users, and at the moment I'm not sure what
version they have. So I reckon I'm better off just leaving it in A2000
format.

Thanks again.

James

p.s. What is an mde file? )

 

[tina]

you're welcome, James.
an mde file is an Access database file with all modules converted to machine
code. this means that forms, reports, and stand-alone modules cannot be
modified. (note converting an mdb file to an mde file has no effect on
tables, queries, and macros.) an mde file is a bit smaller than the mdb file
it was made from, and runs a bit faster because the VBA code has already
been converted to machine code, so no "translation" is necessary at runtime.

if your database is going to have multiple users, standard deployment
recommendation is to split the database into a backed (tables only) mdb
file, and a frontend (all other objects) file, convert the FE db to an mde
file, link the BE file's tables into the FE file, and put a copy of the FE
mde file on each user's hard drive. the commonly shared BE mdb file normally
goes on a server, in a folder to which all users have
Read/Write/Create/Delete permissions. (i should explain that when you
"convert" a db from mdb to mde, the original mdb file is left intact and
unchanged. a *new* db is created from the original, as an mde file. this is
all to the good, because you need to keep a "master" mdb file, so you can
make fixes, updates, and enhancements as needed - then convert the changed
mdb file to mde to distribute to users.)

if you want to read up on these deployment issues re multi-user
environments, here are a few links:
http://www.granite.ab.ca/access/splitapp/index.htm
http://www.access.qbuilt.com/html/multiuser_applications.html
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

hth

 

[James Ivey]

Thanks again Tina.

You're a very good explainer.

)

 

[tina]

you're very welcome

Thanks again Tina.

You're a very good explainer.

)