dangling records (AREV Specific)
At 25 FEB 2005 07:25:01PM Stacy Berger wrote:
I have a record in a table with a key of ' ' I have tried on many occasions to delete this record by doing a select and D. I have rebuilt the index. All to no avail. How can I get rid of this record.
At 25 FEB 2005 08:44PM Ray Chan wrote:
Stacy,
Try this:
Open FileName to File else ….
Key='
Read Rec From File, Key then
Delete File , Key then
doneEndEnd Else
does not existEnd
HTH, enjoy your weekend,
Ray Chan
At 25 FEB 2005 10:56PM Jonathan Bird wrote:
From TCL, issue this command:
DELETE filename "XXX" ""
J
At 25 FEB 2005 11:55PM Donald Bakke wrote:
Stacy,
Is this a problem with deleting the record or is this a problem with the record staying deleted? I'm not quite sure how to read your original post.
dbakke@srpcs.com
At 01 MAR 2005 05:28AM Simon G Wilmot wrote:
Is there another issue here - that the record is correctly deleted but you have a process running somewhere that re-creates it ??
At 01 MAR 2005 07:06AM support@sprezzatura.com wrote:
Relational indexes can do this - if the relationally indexed value is a null.
support@sprezzatura.com
The Sprezzatura Group Web Site
World Leaders in all things RevSoft
At 01 MAR 2005 09:51AM Hippo wrote:
This explains a lot … I have dangling record in one table, too.
It reappears after a while after successful delete. And there is relational index there ("related from" is shown when columns with indexing are listed in DICT field popup … the relation is empty very often).
I am ignoring this record, but I must filter selects (LISTS) adding "WITH @ID" phrase:(.
At 01 MAR 2005 10:24AM support@sprezzatura.com wrote:
It is an attempt to enforce referential integrity.
support@sprezzatura.com
The Sprezzatura Group Web Site
World Leaders in all things RevSoft
At 01 MAR 2005 10:36AM Hippo wrote:
Good try:)
but why this record mirrors data of a real record?
Shouldn't the empty key be created in the opposit table?
(Before thsi discussion I have expected there is something in foggy ends of the application, these record contents typically mirrors new records.)
Is this mirroring typical, or should I search in the fog?