I lostd my database!!!

[NimBiotics]

I've been working on a smal project for the last 2 weeks. My db is in the
new .accdb format. Today, while closing the db I got an error message
stating that access couldn't save my db, but that there was another copy
called database.MDB.
Now, neither my original database is there, nor that database.MDB

Please let me know what can I do to retreive my db!

Thanks a lot in advanced!!!

--
Mario R. Osorio
"... Begin mith The end in mind ..."


Llevo un par de semanas trabajando en un peque#o projecto. Mi base de datos
esta en el nuevo formato .accdb de Access 2007. Hoy cerre la bd, pero tuve
que abrirla inmediatamente, cree una tabla sencilla y la popule con 16
registros que necesitaba tener para su analisys posterior. Al cerrar la base
de datos me dio un mensaje que, por el apuro del momento, no me tome el
tiempo suficiente de leer, pero decia algo como que access no conseguia
guardar mi base de datos, pero que habia otra copia bajo el nombre de
database.mdb.
Lo cierto es que no aparece ni mi base de datos, ni la database.mdb!!
Trate de emular la misma sequencia de eventos y lo unico que pude sacar como
conclusion es que al compactar la base de datos crea otra (copia?) llamada
database.mdb.

Por favor diganme que SI puedo recuperar mi base de datos y como

Muchas gracias por adelantado,

 

[Larry Linson]

If you don't have a very recent backup, you have learned an object lesson in
the value of backing up your databases.

When I am in development mode on a database, I never want to have to repeat
more than an hour's work, so may be making a copy that often. When I have a
database in production, it is always split into front end (user interface)
of which I will have an identical copy from which I can restore, and a back
end (tables with data and relationships), of which I take a backup as often
as the most work I (or the users) can afford to repeat.

Backing up is not much trouble... get everyone out of the DB, and make a
copy of it... in development, I have a folder for the DB called,
unsurprisingly, BACKUPS, and within that folder I create subfolders whose
name is the date and time, eg., 20081032330, into which I just use Windows
Explorer to make a copy.

For my own production, I use a similar convention, but copy the separate
Back End (data) database. For clients' production, we set up folders and
create procedures for backing up consistent with their shop's standards.

Larry Linson
Microsoft Office Access MVP

 

[NimBiotics]

Thanks a lot.

Sorry, unless you backed up your db file somewhere else, it's gone. To
prevent it from happening again, install the hotfix.

http://support.microsoft.com/kb/950812

Chris
Microsoft MVP

 

[NimBiotics]

Thanks for your answer.

If you don't have a very recent backup, you have learned an object lesson
in the value of backing up your databases.

When I am in development mode on a database, I never want to have to
repeat more than an hour's work, so may be making a copy that often. When
I have a database in production, it is always split into front end (user
interface) of which I will have an identical copy from which I can
restore, and a back end (tables with data and relationships), of which I
take a backup as often as the most work I (or the users) can afford to
repeat.

Backing up is not much trouble... get everyone out of the DB, and make a
copy of it... in development, I have a folder for the DB called,
unsurprisingly, BACKUPS, and within that folder I create subfolders whose
name is the date and time, eg., 20081032330, into which I just use Windows
Explorer to make a copy.

For my own production, I use a similar convention, but copy the separate
Back End (data) database. For clients' production, we set up folders and
create procedures for backing up consistent with their shop's standards.

Larry Linson
Microsoft Office Access MVP