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

At 30 SEP 2004 11:58:36AM Ralph Johler wrote:

Our error logging has reported a key with an @FM in it "069@FM7654*0" (where you replace the @FM with the fieldmark character).

I have tried to edit this key directly, without success. The @FM keeps interferring. I do have a program that will readnext the table and search keys for low and high ascii values, it seems like overkill to read a 17,000,000 records to get one bad key.

Anyone have a trick to be able to get at this key directly?


At 30 SEP 2004 12:29PM Matt Sorrell wrote:

Since you know what the key value is, I think you can build the key string programmatically, copy it to another record with a different key, and then delete the record with the bad key.

That way you don't have to scan the whole table to get rid of it.

[email protected]

Greyhound Lines, Inc.


At 30 SEP 2004 11:46PM Pat McNerthney wrote:

Write a little Basic+ program to do it.

Pat


At 05 OCT 2004 11:10AM Ralph Johler wrote:

Yes, a short R/Basic program did the trick.

The 16,500,000+ records where scanned in about 35 minutes, so I spent more time trying to avoid this processing time, than it took!

Thanks all!


At 11 OCT 2004 07:15AM Hippo wrote:

It's common truth, that finding quick answer takes time.

The next time you will need to solve the same problem, you will save almost all 35 minutes.

P.S.: Don't say that codding program which just reads one record (with given key), saves it with different name and deletes it took more than 35 minutes;)

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/9746ecd3a9890b9585256f1f0057c367.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1