Delimiters in Key(s) (AREV Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|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]]


==== Delimiters in Key(s) (AREV Specific) ====
=== At 14 MAY 1999 07:47:03AM Barry Stevens wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
I suspect a client has @fm or @vm in some record keys.

Can anyone paste the code up here that gets rid of them.



Barry
</QUOTE>
----

=== At 14 MAY 1999 09:06AM Matt Sorrell wrote:  ===

<QUOTE>Barry,



I do something like the following to test for delims in record keys:



OPEN "" TO IN.FILE



CLEARSELECT

@REC.COUNT=0

EOF=0

SELECT IN.FILE

LOOP

READNEXT ID ELSE EOF=1

UNTIL EOF

FMIX=INDEX(ID,@FM,1)

VMIX=INDEX(ID,@VM,1)

SVMIX=INDEX(ID,@SVM,1)

IF FMIX OR VMIX OR SVMIX THEN

***do something here like delete or copy to another key value

END

REPEAT

STOP



You can obviously get fancier and more complex, but that should do it for you.



Matt Sorrell

msorrell@movgal.com



</QUOTE>

----

=== At 15 MAY 1999 04:59AM Steve Smith wrote:  ===

<QUOTE>Place a DELIMKEY symbolic in DICT.VOC with formula=



RETURN INDEX(@ID,@FM,1) + INDEX(@ID,@SVM,1) + INDEX(@ID,@VM,1) ...



Then at TCL (with your bad file called SUSPECT.FILE):



LIST SUSPECT.FILE WITH DELIMKEY ] 0 



Should show the culprits (perhaps with keys split on different lines)



Then (in an AREV developer) at TCL on one line type:-



EVAL OPEN 'MYFILE' TO X THEN READ REC FROM X, "BAD":@FM:"KEY" THEN WRITE REC TO X, "GOODKEY"



Steve

</QUOTE>

----

=== At 15 MAY 1999 08:05PM Barry Stevens wrote:  ===

<QUOTE>

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=6162BD7939F4FC5D852567710040BBCA|View this thread on the  forum...]]