I'm using the below program but not having any luck and I cant find any documentation on dtf lookups anywhere.

vstring = @xlookupsourcelistall("C:\Q&A\Inventory.dtf", Stock Number, "Stock #", "Invoice date;Sold by")

where:

Stock number is LE in sesame that contains a matching number to lookup in Q&A

Stock # is the field name in Q&A

Invoice date and Sold By are fields in Q&A containing the data I want to lookup.

I suspect I'm entering the path and filename wrong. Any thoughts?

Thanks,
Steve

does your @xlu work if you only have one source element eg "invoice date" ?

Uhoh. Now I'm getting an error message inQ&A saying "This is not a q&a database.".

I wasn't getting this error before i tried the xlookups.


I give up.

Steve

Pineberry,

Thanks for the suggestions, but still no luck. Only @error is being returned.

However, Using the @xlookup versus xlookupsourcelistall is not 'corrupting' my Q&A database.

Steve

Bob, Thanks for your feedback.

I saw the typo and worked around it, but still no luck.

Are your q&a databases opening up ok after using Sourcelistall?

Steve

Yes, I have a backup from 8/13, not all is lost!

Will let Erika and Mark work on this one.  Cannot risk real data.

Thanks for asking about that Steve.  I saw no messages, but did not look at the server log.  Will check that out now.
======
From the log:
Failed to open n:\data\qa5\ss\db\actions.dtf - incorrect version or format.

With the exception of XListValues, "X commands" that didn't exist in Q&A are not supported on Q&A databases. So:

XLookupAll
XLookupSourceList
XLookupSourceListAll
XPostAll

do not support Q&A .dtf files!

Bob,
It is likely that your .dtf file is only very mildly corrupt. The header string that starts every .dtf file reads:

SYMANTEC TOUCHBASE DATABASE

After you ran XLookupSourceListAll on that file you will see that the first 12 bytes have been overwritten (% = denotes junk):

%%%%%%%%%%%%CHBASE DATABASE

If you use your favorite ASCII TEXT EDITOR (I am not aware of any microsoft product (including notepad, wordpad, or MSWord) that qualifies as an ASCII only editor) you can replace those bytes with "SYMANTEC TOU" and save the file (use a backup). That should restore your .dtf to its original state.

The corruption occured, not the first time the XLookupSourceListAll failed to open the file - but the subsequent attempts on the same run. The command does set the @error flag to indicate the failure, and writes a message to error log indicating that it does not recognize the file type.

I have fixed the bug that caused it to erroneously believe that the file had loaded. The fix will be in the next release. I will also notify the folks in charge of documentation to explicitly state which XLookup extension commands support Q&A files (or I will get the new commands to work on Q&A files for the next release).

I am personally sorry for the missunderstanding.

Please be aware that this does not affect XLookup, XLookupR, XUserSelect, XUserSelectR, and XListValues, which should work on any .dtf files without corruption.

Supports Q&A Files:
XLookup
@XLookup
XLookUpR
@XLookUpR
XUserSelect
@XUserSelect
XUserSelectR
@XUserSelectR
@XListValues

Only Supports Sesame Files:
XPost
XPostR
XPostAll
@XLookupAll
@XLookupSourceList
@XLookupSourceListAll

Just one more small clarification re XPost, XPostR.:

You list 6 commands in lower section that summarizes, Only Supports Sesame Files

But in the section near the top where you list 4 exception files:
Quote:

XPost and XPostR did exist in Q&A, but are not listed there. 

Doesn't that mean that they should be listed in the group that work in both Sesame and Q&A?  But they are shown in the group that does not work with Q&A.  This conflicts with the earlier statement.

So is the final summary at the bottom of the posting, Only Supports Sesame Files, the correct listing and the earlier comment was not correct?