If no spaces, then the quotes and the semi-colon terminator work, else you
remove the quotes, pad the space with a comma (for AND), and remove the
semi-colon terminator...GEEZ.

Of course, one wonders what would happen if the second part of the key's
actual value started with a space rather than the first part of the key's
value ending in a spaces...would probably do the same as mentioned above,
except also have to set your screen to blue background with green
foreground... :-)

I loosely understand that there may be a no-parse option on the ODX build
key command, but hey, this is a one-timer...

Thanks to all that replied.

Ray Shahan

"Life is what happens while you're busy making other plans", John Lennon

> -----Original Message-----
> From: Shahan, Ray
> Sent: Thursday, September 19, 2002 10:26 AM
> To:   [log in to unmask]
> Subject:      OMNIDEX
>
> Hi all,
>
> I'm doing a DBFIND using an Omnidex key built with:
> CREATE CATALOG-ITEM MULTIPLE FROM XREF-SOURCE[1:4] & EDA-ITEM
>
> If my key is (and the quotes are part of the key's value "SSF1567785",
> everything looks good, but if my key value has a space "JLH 1567785", then
> the DBFIND fails.  I'm assuming there's a parm on the key build that's
> missing (or incorrect), but my Omnidex skills are minimal...
>
>
> Any clues/help?
>
> TIA
>
> Ray Shahan
>
> "Life is what happens while you're busy making other plans", John Lennon
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *