I just tested your theory, and I was able to recover my deleted table. This
is what I did: I copied a working Access 2K mdb file, and opened the copy.
I created a new test table, then deleted it. Then I deleted another table.
Then I created a new query, a new form and a new module. In the new module,
I copied the code from the Access 2K recovery method and pasted it into the
module, saved and compiled. Then I created another new table. All of these
activities wrote to the db file.
I ran the code and recovered not only the table I deleted, but the first test
table I created and deleted.
So you must have done something more than just write to the db in a new
module for the code to fail. Did you close the db prior to the recovery?
The code won't work if you close, then reopen the db.
You can find services on the Internet that will recover your deleted table,
but they're expensive. It's best to have recent backups.
Chris
Microsoft MVP
MLH wrote:
>Yeah, but if you've done ANYthing at all that writes to db, won't
work. Even creating the module, pasting the code to it and saving
it renders the table unrecoverable. I won't be without this code
snippett in my future endeavors. Repopulating the table was not
an enjoyable task. I was hoping some third party utility would
dig deeper & do a bit more. Thx 4 comments.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xx
>>If undo doesn't work and you havn't closed the file, follow Microsoft's
instructions.
[quoted text clipped - 16 lines]
>>>>TABLE tab of database window with
the DELETE key?
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200805/1 
