Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

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
  • done
  End

End Else

  • does not exist

End

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.

[email protected]

SRP Computer Solutions, Inc.

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 [email protected] wrote:

Relational indexes can do this - if the relationally indexed value is a null.

[email protected]

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 [email protected] wrote:

It is an attempt to enforce referential integrity.

[email protected]

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?

View this thread on the forum...