Access Convertion 97 => 03

[Guest]

Hi,

I'm currently converting some Access 97 files to Access 03.
Does the file size increase significantly as it is converted? If yes, why?
Is there anything that I can do to reduce the size?

Thanks

 

[strive4peace]

Hi Lucia

yes, more information is stored

you can compact/repair after your convert
(Tools, database Utilities)

when you compile your code, you may need to preface DAO objects when you
Dim them

ie:

Dim rs as DAO.recordset



Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote Programming and Training
strive4peace2006 at yahoo.com
*

 

[ruralguy via AccessMonster.com]

Hi Lucia,
MVP Allen Browne has written a web page on the subject:
http://allenbrowne.com/ser-48.html

Crystal is an MVP too!

 

[Guest]

Thanks!

Hi Lucia

yes, more information is stored

you can compact/repair after your convert
(Tools, database Utilities)

when you compile your code, you may need to preface DAO objects when you
Dim them

ie:

Dim rs as DAO.recordset



Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote Programming and Training
strive4peace2006 at yahoo.com
*

 

[Guest]

Hi, Lucia.

Does the file size increase significantly as it is converted?

Yes. Expect it to about double.

If yes, why?

Access 2003 uses Jet 4.0 as the database engine, which allows Unicode
characters, so two bytes are stored for a single character, not one byte as
in Jet 3.5. Jet 4.0 databases allow twice as much room for data than the
Jet 3.5 databases for Access 97, so Jet 4.0 databases can hold up to 2 GB,
while Jet 3.5 databases can only hold up to 1 GB of data.

Is there anything that I can do to reduce the size?

Yes. Compact the database afterwards. But the good news is that you don't
have to worry about adding the DAO 3.6 Object library, because it's there by
default in Access 2003, so pasting code from Access 97 databases will still
work in Access 2003. Access 2000 and 2002 had problems with some of the
common DAO library objects, because the ADODB library was the default data
access library, and DAO code copied from Access 97 would often get data type
mismatch errors.

If you ever add ADO code to this database, you'll need to disambiguate the
Recordset, Field, Properties, and other objects that are included in both
the ADODB and DAO libraries. Please see Access MVP Tom Wickerath's article,
"ADO and DAO Library References in Access Databases," on the following Web
page for more information:

http://www.Access.QBuilt.com/html/ado_and_dao.html

You'll find more articles and tutorials on the following Web page:

http://www.Access.QBuilt.com/html/articles.html

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[strive4peace]

As usual, Gunny, you have added some great information! Thanks

Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote Programming and Training
strive4peace2006 at yahoo.com
*

 

['69 Camaro]

Hi, Crystal.

Thanks. Just helping out where needed.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.