Access 2000 file format vs. Access 2000 - 2002 file format

B

Buck

I have two separately licensed installations of Access 2003, one at
work and one at home. The blue bar at the top of both installations
says something like:
"db1 : Database (Access 2000 file format)".

Yesterday at work I notice a coworker's Access 2003 blue bar says:
"db1 : Database (Access 2000 - 2002 file format)".

If my coworker and I used the same installation disk then why the
difference in file formats?
 
C

Craig Alexander Morrison

No, it will say Access 2002 - 2003 file format"!

You just change the setting in the advanced tab of options or explictly
convert to the relevant version for the database you have.

Access 2002 and 2003 use the same new format and they also use Access 2000
(when installed this is the default)

Use Access 2002/2003 for better stabilty and use with Access 2002/2003 MDEs.

Use Access 2000 for backward compatibility for the poor sods who still use
Access 2000.
 
G

Guest

Use Access 2002/2003 for better stabilty...

Says who? While I agree that you need to convert to this format to create a
..mde file, this is the first time I've ever read an opinion that the
2002/2003 file format results in better stability. In fact, Microsoft even
gives people a reason why they may want to stick to the 2000 file format
during their development work:

Database bloat is not stopped by compacting database with Access 2002 format
http://support.microsoft.com/?id=810415


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

No, it will say Access 2002 - 2003 file format"!

You just change the setting in the advanced tab of options or explictly
convert to the relevant version for the database you have.

Access 2002 and 2003 use the same new format and they also use Access 2000
(when installed this is the default)

Use Access 2002/2003 for better stabilty and use with Access 2002/2003 MDEs.

Use Access 2000 for backward compatibility for the poor sods who still use
Access 2000.
 
C

Craig Alexander Morrison

I think you'll find the use of decompile and not using track name
autocorrect will avoid that application problem, or even if it doesn't I use
them and have never had the problem. BTW you can also use the
SaveAsText\LoadAsText commands to create a full backup and restore a clean
application without these problems.

Another advantage to using 2002/2003 for your database is that it stops
Access 2000 from accessing your data, always a good thing to stop.
 
G

Guest

Hi Craig,

Your first paragraph includes advice that can be done using the Access 2000
file format just as easily as using the 2002-2003 file format.

As for the second paragraph, I only distribute the front-end as a compiled
..mde file, therefore I have converted it to the 2002-2003 file format first.
So, it's really not an issue for me.

Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

I think you'll find the use of decompile and not using track name
autocorrect will avoid that application problem, or even if it doesn't I use
them and have never had the problem. BTW you can also use the
SaveAsText\LoadAsText commands to create a full backup and restore a clean
application without these problems.

Another advantage to using 2002/2003 for your database is that it stops
Access 2000 from accessing your data, always a good thing to stop.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top