How do I revert .accde to .accdb?

[kblakedunham]

I'm fairly new to Access in general, and am using 2007. I created a simple
database and I was experimenting with some features. I ended up converting
it to an .accde database. I need to make other changes to the database, and
I don't know how to undo the .accde conversion. I've changed the file
extension back to .accdb - and it still opens as if it was .accde. I don't
know what else to do. I'm trying to avoid starting from scratch. If anyone
can help, it would be greatly appreciated.

 

[Klatuu]

You should still have the accdb version. When you make an sccde, it doesn't
replace the accdb, it only uses it to create the accde.
Sorry, but the internal format has been changed and you can't get it back.
the accde is specifically designed to prevent users from making any
modifications.

 

[Douglas J. Steele]

There is no "undo" capability. When you created the accde, you needed to
keep the accdb for situations such as this.

Note that you also need to split your application into a front-end
(containing the queries, forms, reports, macros and modules), linked to a
back-end (containing the tables and relations) so that existing data isn't
impacted by changing the application. Note that there's no point in
converting the back-end to an accde.

 

[markinboone]

So what would be the basic steps to get data added to an ACCDE file merged
into the original ACCDB file? Or is there a way to keep them in synch?

 

[John W. Vinson]

So what would be the basic steps to get data added to an ACCDE file merged
into the original ACCDB file? Or is there a way to keep them in synch?

You should probably not be storing *data* in an ACCDE file *AT ALL*. You can,
but the most recommended solution - especially for multiuser systems - is to
store data in a "backend" accdb (or SQL/Server Express or any of dozens of
other data stores), and use a .accde file as a frontend, linked to the tables.

That said, there is nothing at all difficult about adding *data* to existing
tables in an accde file. You can use forms to edit or enter data; enter data
directly into table datasheets; import data... it is NOT necessary to convert
back to a accdb file. The only thing you can't do in a accde which you can do
in an accdb file is change the actual *DESIGN* of the forms, reports, or
tables. You can change the content without changing the design.

 

[daiku]

I've got the same problem: I created an accde file and kept the data
in it. I see now how I should have linked back to the accdb. But,
here I am with stale data in the accdb, and the fresh data in the
accde. How can I copy the data from the accde back to the accdb, so I
can start over and do this the right way? It's just one flat table.
CB.

 

[Larry Daugherty]

First, make a backup of your accdb with a different name. Next delete
the affected tables from the accdb. Get External Data from the accde.
Copy in the complete tables.

Note that you can almost always get at the data in an MDE or ACCDE.
You just can't get at the design.

Typical implementations have the BackEnd in an MDB or ACCDB. The
FrontEnd is usually deployed as an MDE or ACCDE (linked to the
BackEnd) so that users can't inadvertently alter the developer's
design.

HTH
--
-Larry-
--

I've got the same problem: I created an accde file and kept the data
in it. I see now how I should have linked back to the accdb. But,
here I am with stale data in the accdb, and the fresh data in the
accde. How can I copy the data from the accde back to the accdb, so I
can start over and do this the right way? It's just one flat table.
CB.