
Acc 97 Strange Table Behavior
I have seen this a lot with SQL tables - what happens is Access can no
longer locate the primary key of the table - this usually happens when the
primary key index gets corrupted at the source table (SQL in my case, the
attached MDB in yours)
One sure fine way to verify this is to open the table as an attachment- it
will not display the "New" blank record, now open the table in the local
database, and it will look fine (This is in the case of SQL, access mdb's
may behave a little different) -
If this is the case, look at the indexes of the table you are attaching to,
often, access will create two unique indexes for the primary key of the
talble, one called "PrimaryKey" and one with the field name - delete the one
with the field name (You only should have one index that containes the
primary key of the table, and it sould be called "PrimaryKey" -- This
applies to Access tables, the rules for SQL a different)
After deleting the extra indexes, import all of the tables from the database
(Data database, not Application DB) into a NEW database, this will repair
any problems with the MSys tables - repair and compact the new DB, and all,
hopfully will be fine!
Dale Dennis Lotts
Quote:
>I am running Access 97 on WinNT Service Pack 3.
>I have a database filled with forms. The same database is linked to
several
>tables in another database. There are no records in the tables in the
>second database.
>When I initially opened the forms, all was well. I could see all the
>controls. However, when I closed the form and then reopened it, I couldn't
>see anything but the header. I know that this happens when there are no
>records in the underlying table, so I checked the table.
>The table did not have any records. In fact, it didn't even have a single
>blank record that I am accustomed to seeing in order to enter the first
>record.
>A quick check of the other tables in the linked db found them to all be
>exhibiting the same behavior.
>So, I replaced the .mdb file with a backup copy. When I looked at the
>tables in that .mdb file, they were fine. Once again, they had no records,
>but they did have a single blank record where I could enter the first
record
>in the table.
>After opening, closing, and reopening the form, the tables in the database
>were once again void of even a single blank record.
>Has anyone seen this behavior and how can I fix it?
>Thanks,
>Galen Mayfield