I have a pdx10 expenses database of 40,800 records and growing. Every
few months about 400 of those records disappear. It's not a filter or
viewing problem. Very odd: it's always the same 400. It's no real
trouble right now as I have the missing 400 in a separate db and just
add them back when they go missing. It seems to happen when I am
developing some code and get lots of the error messages that are
essentially fatal and require me to re-start paradox. The corrupt db
files are larger than the new db file I create from adding the corrupt
file and 'missing.db' into a new db.

Any ideas? I would like to get to the root of the problem as I am ever
suspicious that perhaps smaller numbers of entries are going missing.

when you have a damaged table, you do NOT keep passing it along.. that's why
it never goes away..

make a complete backup, fix the table with the repair tool, validate the
results, and move on..

--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

"Fred Z" <fredzcalgary (AT) hotmail (DOT) com> wrote

Sounds like YOU are corrupting the data when you crash during development.
Corrupt tables will often lose data. You should develop on a COPY of the
data, not the live data.

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and non-profits
since 1982

Fred,

I looked around here... but haven't seen a thing. What do they look like?
Could you identify these records with any level of certainty if you were to
see them in a group with other records?

I'll keep looking around here... but I would be willing to bet that they're
probably sitting around somewhere at your place.... or maybe they've been
stolen. It's hard to say. I'll look in the garage next.

)


Sorry Fred... I just had to do it... It's been a LONG LONG day around here
with very little progress.... I'm ready for a scotch. )

I'm sure you'll get some professional guidance here on the matter. Good
luck.

--
....
`·.¸¸.·´¯`·.¸¸.·´¯`·-> rodney

Fred Z wrote:

If the database is in-service and has been for some time, and if the problem
is as repeatable as you describe, then in my opinion you are dealing with a
subtle application bug.

Obviously, there -could- be an issue related to the "lots of error messages
that are essentially fatal" (a curious notion, if you stop and think about
it... ;-) ... ) and whatever causes you to be "required to re-start
Paradox" obviously deserves both a closer look and a lot more explanation.

But that could also be a good ol' red herring. True database corruption
errors (and, umm, I oughta know) are usually much more catastrophic than
that. And more unpredictable. Even "a damaged table" is not too likely to
allow you to say "always the same 400."

For instance, what if the "missing" records really aren't missing, but were
overwritten with other data? What if there's a subtle bug, a locking issue
or what have you, maybe a "delete all the old records and insert these new
ones" type of logic-sequence, which UNDER CERTAIN CASES -- well-defined but
as-yet unknown to you -- does not work and causes record loss?

Whatever the bug turns out to be .. "those 400 are like that."

----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com