Records missing after relinking table

[Me.Frustrated = True]

A couple of years ago when I was (more) foolish, someone convinced me to move
a couple of years' worth of old records from one of my tables into a new,
"archive" database, while keeping the more current records in our regular db.
I did the move at the time, but then I decided the other day to move them
back into their original table in the backend.

The move went fine, and all the records were there. But when I went into
the front end to relink the table, after relinking I lost about the last 19
days worth of records - several thousand of them. The records were right
there, in the table in the back end, just before I relinked the table. But
right after I relinked, BAM! the records were gone. They weren't just not
showing up in the form, they are completely gone from the table.

Has anyone had any experience with records disappearing like this?

 

[Jerry Whittle]

1. Make double sure that you moved the records from the database where they
were located to where you think that you need them. I've had experience
moving things to places where I didn't mean to!

2. If you imported the records, look for a table named the same but with
something like Export Errors in the table name. If you changed something in
the current table but not in the archive table, it's possible that those
records didn't get imported.

3. Make sure that you've relinked to the correct BE.

4. Do a compact and repair.

 

[Me.Frustrated = True]

Thanks for your reply, Jerry.

I moved all the records via an append query, and the old records transferred
over fine. The ones that are missing are the most recent records, from Feb
3rd until this morning - all wiped out. I'm kicking myself now for not
performing a backup on the back end before I decided to do the append.

I learned a big lesson this morning. Hopefully I can keep my job after
this.... these records are a state requirement, the fact that they have
disappeared is a big deal and I should have known better!

Everyone - all you new users and experienced ones alike - back up your work
first !! Don't make the same mistake that I did.

 

[John W. Vinson]

The move went fine, and all the records were there. But when I went into
the front end to relink the table, after relinking I lost about the last 19
days worth of records - several thousand of them. The records were right
there, in the table in the back end, just before I relinked the table. But
right after I relinked, BAM! the records were gone. They weren't just not
showing up in the form, they are completely gone from the table.

Just double and triplecheck that you don't have any Filter set on the table,
and that you're not making any assumptions about the records appearing at the
end of the table or the beginning of the table. The sort order of records in
the table is arbitrary - I *hope* the records are there, just not in the order
you expect, or inadvertantly filtered out of view.

 

[David W. Fenton]

=?Utf-8?B?TWUuRnJ1c3RyYXRlZCA9IFRydWU=?=

The move went fine, and all the records were there. But when I
went into the front end to relink the table, after relinking I
lost about the last 19 days worth of records - several thousand of
them. The records were right there, in the table in the back end,
just before I relinked the table. But right after I relinked,
BAM! the records were gone. They weren't just not showing up in
the form, they are completely gone from the table.

The two main causes that spring to mind that nobody has yet
mentioned:

1. corrupted index. Make a copy of the back end and compact it. If
an index is corrupted, it should tell you. If it doesn't check to
see if there's an MSysCompactErrors table.

2. you're not linking to the back end you think you are. This is
pretty unlikely, but, hey, sometimes "it's not plugged in", i.e.,
sometimes the most basic things trip us up because we're assuming
problems are more complex than they are.

 

[Me.Frustrated = True]

I was almost too embarrassed to post this.
A few weeks ago I moved the whole back end to a different location. I had
forgotten all about it, and was appending records to the wrong backend. So,
nothing is missing, and I feel like a heel for freaking out about it.

Thanks anyways for all your replies Mr. Whittle, Mr. Vinson, and Mr. Fenton.

 

[John W. Vinson]

I was almost too embarrassed to post this.
A few weeks ago I moved the whole back end to a different location. I had
forgotten all about it, and was appending records to the wrong backend. So,
nothing is missing, and I feel like a heel for freaking out about it.

I know how frustrating that can be (I once worked for several days on a
complicated frontend database... which had been superseded by a new one months
before). I'm glad you got it figured out and that we don't have to worry about
what would be a dreadful bug!