I've got a "PlayPen" version of a production app on one user's C: drive - so
they can do what-if scenarios without messing with the production data.
The prod version has been running for going on seven years now with virtually no
data problems. (Well, ok, somebody pulled a cable in the LAN closet once and
corrupted the DB....but that's about it...)
The playpen version only gets used sporadically, but just the other day the
users said goofey things were going on.
One person swears that a bunch of "Issuers" (this is a bond trading app..)
spontaneously changed and another person (using the app at person #1's PC) says
they entered a couple of bonds and at least one child table entry disappeared
over the course of the day.
Personally, I'm hesitant to take all this at face value - in spite of how
certain both people seem to be about what they've experienced.
For the "issuer" to have changed, either the record's "IssuerID" field would
have to have changed or the tlkpIssuer table would have had to been shuffled.
Seems to me that when things go wrong at that level in a DB, things get *really*
messed up - as in checksums not adding up right and the DB coming up as corrupt.
Before I leap into this, I'd ask if anybody has experienced anything similar.
?
-----------------------
PeteCresswell
