Solved Transforming database from 2010 model or higher to 2003.

FeelCore

New member
Local time
Today, 06:25
Joined
Aug 20, 2025
Messages
17
Hi, i wanted to know is there simple way to transform my database to older type?
i know you all will be looking at me like i am crazy, but its not my power for that decision.
I tried just to save as version, Blocked.
i tried to remove all combo box and long text fields in tables, no go anyway.
Maybe someone has done it or is pro to this?
 
You already tried the simple way; but if it failed, then that means you'll have to do it the hard way.
 
You could create and mdb and try to import all of the objects from this accdb into it.
 
Can you be a bit more specific? Are you looking to change the DB format to an .MDB or are you very specifically seeking to be able to run the DB on an old version of Ac2003?
 
You could create and mdb and try to import all of the objects from this accdb into it.
Gasman beat me to the "WHY?" question.

What problem would be solved by downgrading the accdb to an mdb?
 
You could create and mdb and try to import all of the objects from this accdb into it.
Would an old version be able to read an accdb though? I thought the structure changed a fair bit?
 
There are "export to text" and "import from text" options that you can try, and those will "smooth over" some ... SOME ... of the differences. If the DB is still an .MDB then data might be still retrievable using DAO recordset methods. If the DB has gone all the way to .ACCDB, it gets trickier.
 
Would an old version be able to read an accdb though? I thought the structure changed a fair bit?
Let me rephrase.

You could use Access 2010 (or newer) to create an empty mdb. Then you could try to import the objects from the accdb into the mdb using Access 2010 (or newer).

Also, I should acknowledge that I did interpret this phrase, "...transform my database to older type" and the post title to mean that the OP has an accdb (newer format) file that needs to be downgraded into an mdb (2003 format).
 
Can you be a bit more specific? Are you looking to change the DB format to an .MDB or are you very specifically seeking to be able to run the DB on an old version of Ac2003?
i want to downgrade or transform my newer to older version, client will use old access (dont ask why) and i need my newer type DB to downgrade to older
 
Let me rephrase.

You could use Access 2010 (or newer) to create an empty mdb. Then you could try to import the objects from the accdb into the mdb using Access 2010 (or newer).

Also, I should acknowledge that I did interpret this phrase, "...transform my database to older type" and the post title to mean that the OP has an accdb (newer format) file that needs to be downgraded into an mdb (2003 format).
It would appear not.?
I just created a mdb (actually that was the default? in 2019) and tried importing.

Edit: Saying that, I did get all the forms, queries, reports, macros & modules.
I then tried on my BE and managed to get all the tables.


Way to go George! (y)
1757598957445.png
 
Last edited:
i want to downgrade or transform my newer to older version, client will use old access (dont ask why) and i need my newer type DB to downgrade to older
Just get the runtime for your version.
 
EDITED to correct some over generalised comments:
You may not be able to import all objects from an ACCDB to an MDB because the older file version has no knowledge of the newer ACCDB file format features. You also cannot link to tables in an ACCDB file or use an ACCDB file as a library reference.

For the same reasons, you can't save an ACCDB to MDB if the file contains features not available in the older version.
Neither lookup fields or long text (memo) fields are relevant to this situation.

Things that may cause problems include:
  • new field types - attachment fields, MVFs & column history, calculated fields
  • new datatypes e.g. large integer AKA bigint, date/time extended
  • new control types e.g. navigation control, modern chart, 'new style' tab control(?)
  • newer default sort order
In fact, Access lists many of these in the error message shown if there are multiple issues

1757599556160.png

Even if you have none of the other issues, the sort order has often been the problem for me as its easy to overlook.
This error will be seen if its the only problem:

1757599738013.png


In Database Options | General, change the default sort order from e.g. General to General Legacy

1757599965416.png


The database should then convert to MDB successfully

EDIT: I've just written this up as a new web article for future reference:
 
Last edited:
Would an old version be able to read an accdb though? I thought the structure changed a fair bit?
No. A2003 was mdb only.
Mdb will still run on current versions.

When you change an mdb to an accdb you get warnings, so I guess it's not trivial to reverse the process even if you don't use advanced constructs.
 
Don’t think the OP has said what the newer version is - if 64bit, it may not convert to 32bit mdb.
 
You can't import to a MDB from an ACCDB because the older file version has no knowledge of the ACCDB file format

The reason why you can't save an ACCDB to MDB is because the file contains features not available in the older version.
Neither lookup fields or long text (memo) fields are relevant to this situation.

Things that may cause problems include:
  • new field types - attachment fields, MVFs & column history, calculated fields
  • new datatypes e.g. large integer AKA bigint, date/time extended
  • new control types e.g. navigation control, modern chart, 'new style' tab control(?)
  • newer default sort order
In fact Access lists many of these in the error message shown if there are multiple issues

View attachment 121471
Even if you have none of the other issues, the sort order has often been the problem for me as its easy to overlook.
This error will be seen if its the only problem:

View attachment 121472

In Database Options | General, change the default sort order from e.g. General to General Legacy

View attachment 121473

The database should then convert to MDB successfully

EDIT: I've just written this up as a new web article for future reference:
While it true that you can't export tables with newer features, such as support for Large numbers and Date Time Extended, from an accdb to an mdb, it is also true that plain vanilla tables CAN be exported from an accdb to an mdb, as I just did.

By modifying your tables to avoid such conflicts first, you should be able to import them, along with other objects.

Or, as Colin shows, you can manage the accdb so that it is successfully saved down to the mdb format. That's undoubtedly less work.
 

Users who are viewing this thread

Back
Top Bottom