Re: DBC Corruption

• Previous message: Dale Beitz: "DBC Corruption"
• In reply to: Dale Beitz: "DBC Corruption"
• Next in thread: Dale Beitz: "Re: DBC Corruption"
• Reply: Dale Beitz: "Re: DBC Corruption"
• Messages sorted by: [ date ] [ thread ]

Date: Fri, 23 Apr 2004 12:37:28 -0700

Your problem is atypical - you can, in fact, routinely perform such edits.
Have you tried cleaning up the project? [Open the project, then select
Project | Clean up from the menu].

 - Rush

"Dale Beitz" <anonymous@discussions.microsoft.com> wrote in message
news:F2639082-693D-4506-8BCC-CBD399BE9770@microsoft.com...
> Greetings!
>
> I'm developing a FoxPro 8.0 (with SP1) application using a database
container. The application has not yet been released to production so it
has no "real" data in the tables, but they do contain test data. Whenever I
try to change the referential integrity of a relationship to establish a
cascading delete from a parent to a child table, I get an error message that
reads ".dbc internal consistency error". If I select the help on the error
dialog, it tells me that the error is 1550 and to use VALIDATE DATABASE to
correct the problem, or delete the DCX file so it can be recreated.
>
> First, I can't get the error dialog to go away. I can click OK dozens of
times, and it just keeps coming back. I have to use task manager to kill
FoxPro, which could be contributing to the corruption. After re-opening
FoxPro I've tried both of the suggested fixes (validate and rebuild the
DCX), and neither fixes the corruption. The validation tells me several of
my talbes are "missing required information". If I do VALIDATE DATABASE
RECOVER it will delete the offending tables from the container, but then
when I add them back in I've lost all my long file names, relationships,
etc. I've got a backup copy of my uncorrupted database that I can revert
to, but I still need to make my desired edits to it. And I can run a
validate against this backup and it comes back clean, so I know itâ?Ts good.
I'll also mention that the database container contains a local view, since
one of my coworkers seems to think that it might be involved in the problem.
But I can delete the view and I still get the same error when I edit the
referential integrity of the relationship. I've also ZAPPED all the tables
in the container, to no avail. I've also deleted the relationship and
re-created it from scratch (which it allows me to do), but as soon as I try
to set the cascading delete I get the error.
>
> I had the same error very early on shortly after I created the data
structures, and ended up having to delete the container and all the DBF
files and re-create the entire data structure from scratch. I'd really
rather not have to do that at this point, given that the structure is much
more complex now.
>
> Is there some trick to editing a database container once the initial
design work has been completed? It seems like the benefits of using a
database container would be negated by the inability to do maintenance to
the container if there isn't some easy solution to this sort of thing.
>
> Thank you in advance,
>
> Dale Beitz
> Michigan Hospital Association
>

• Previous message: Dale Beitz: "DBC Corruption"
• In reply to: Dale Beitz: "DBC Corruption"
• Next in thread: Dale Beitz: "Re: DBC Corruption"
• Reply: Dale Beitz: "Re: DBC Corruption"
• Messages sorted by: [ date ] [ thread ]