Serious Bugs with "compact and repair"

[Mark J.]

I had a problem where some dummy entered duplicate help tickets in our
database, the way it is linked there are also comments that correspond to
each help ticket number. To make a long story short, the duplicate ticket
numbers caused an error that made our reports unusable which give the error
"Record has been deleted." It doesen't specify which one, so I did a "compact
and repair" well we enter comments in using a subdatasheet nested in the help
ticket table. It is how we have always done it and this is the most efficient
way to do it. But when I did the "compact and repair", it destroyed all the
subdatasheets now it just shows the ticket number and the comments
subdatasheet is gone! the reports work fine now, though. Is there anyway to
do a repair to fix the rports but not destroy the setup of all nested
subdatasheets?

 

[Dirk Goldgar]

I had a problem where some dummy entered duplicate help tickets in our
database, the way it is linked there are also comments that
correspond to each help ticket number. To make a long story short,
the duplicate ticket numbers caused an error that made our reports
unusable which give the error "Record has been deleted." It doesen't
specify which one, so I did a "compact and repair" well we enter
comments in using a subdatasheet nested in the help ticket table. It
is how we have always done it and this is the most efficient way to
do it. But when I did the "compact and repair", it destroyed all the
subdatasheets now it just shows the ticket number and the comments
subdatasheet is gone! the reports work fine now, though. Is there
anyway to do a repair to fix the rports but not destroy the setup of
all nested subdatasheets?

I'm not sure exactly what has happened, but it sounds like you may just
have lost the indication in the table design that it should display a
subdatasheet based on the Comments table (whatever that table may be
called). You might try the following to see if you can get your
subdatasheet back:

1. Open the Help Ticket table in design view.

2. Open the property sheet for the table. It should say "Table
Properties" in its caption bar.

3. On the "Subdatasheet Name" line of the property sheet, enter the name
of the table you want to show in the subdatasheet.

4. On the "Link Child Fields" and "Link Master Fields" lines, enter the
names of the fields that link the two tables.

5. Save the design changes.

6. Open the table in datasheet view and see if your subdatasheet is back
the way you had it.

 

[Mark J.]

I tried that it will either show all the comments for all of the tickets if I
put "comments" table in one of the two "link child or parent fields boxes",
or if I put the "comments table" in both it will give me an error when I
try to expand them, "Your have entered in an expression that is to
complicated to evaluate."and it wont expand but yet it has a "+" to expand.

 

[Dirk Goldgar]

I tried that it will either show all the comments for all of the
tickets if I put "comments" table in one of the two "link child or
parent fields boxes", or if I put the "comments table" in both it
will give me an error when I try to expand them, "Your have entered
in an expression that is to complicated to evaluate."and it wont
expand but yet it has a "+" to expand.

What is the actual name of the comments table, and what are the names of
the fields in each table that are related? That is, what fields link
the two tables?