| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Oracle/Paradox problem
I'm a Paradox developer from the 1.x days. My employer recently had me convert many Paradox/Win apps over to an Oracle 7.1 backend, using the BDE SQL-link drivers from Borland, and I was quite successful in retaining the Paradox frontends through this conversion.
With one app, tho', actually, one table in the app, I've been having a problem that seems to be growing over time. After a few months of successful use, first one then another user would report that they were unable to edit certain records because "another user has changed that record", when, in fact, no other user was logged in. In time, those few
users were unable to edit ANY record. For them, I worked out a
local-table workaround, flagging the edited records, then "Adding" them
back to the Oracle table when they were finished. This worked, for a
few
weeks. Suddenly, the "adds" were not taking -- no error messages, but
the
data wasn't changing.
Concurrently, more and more users were getting these same errors, until,
this past month, NO user could edit a record directly. I've had to
resort
to a brute force method of updating the database -- emptying the SQL
table, then adding the entire local table back in. This, of course,
opens
a can of worms regarding concurrency.
I've deleted and recreated the table a number of times. At first, this helps -- everyone can edit, the "adds" stick, etc. But, with time, this
ability degrades, and I'm back to workarounds.
Let me reiterate, it is only ONE TABLE that exhibits this behavior.
There
are MANY MORE tables on the server and in the tablespace that do NOT
acts
this way.
Any clues? I'd be most grateful.
Thanks
--
 |
 |