From your example, it appears that you have a form named "Vo2_Max" and a LE named "Vo2 Max" on that form, as well as a LE named "Vo2 Max" on the current form. I recommend that you rename at least the form, so as to reduce the possibility of calling something "Vo2 Max" when you meant "Vo2_Max" or vice-versa.

You might try:

var vTmp as string

  vTmp = @ xlu(@fn, Time to Reach , "Vo2_Max!LE3", "Vo2 Max")
  if(@Error)
  {
    WriteLn("XLookup produced an error.")
  }
  else
  {
    Vo2 Max = vTmp
  }
 

If Vo2 Max is a number (not a string), replace the line:

Vo2 Max = vTmp
 

with:

Vo2 Max = @ToNumber(vTmp)
 

Ah - this is one of those times when I really wish 2.0 was out already. It has command that can tell you more than @Error as to the actual nature of the error.

Are you absolutely sure that there is a matching value between FETime and TBLvo2Max!TblTime? If at all possible, try using two string LEs and (for test purposes), set both LEs to exactly the same string. It may be easiest to simply hardcode the key string right in the @XLookup:

vTmp = @XLookup(@Fn, "Test Value", "MyForm!MyLe", "AnotherLE")
 

assuming in the case above that you have already put the string "Test Value" in the LE called MyLe in the form "MyForm". See what I mean?

I am not sure how the string "apple" corresponds with the string "good".

Are you in preview mode?

Try putting the string "test me" in Source!TblTest, and run the following (not in preview mode):

var vTmp as STRING

  vTmp = @xlu(@fn, "test me", "Source!TblTest", "TblRESULT")
  if(@Error)
  {
    WriteLn("XLookup produced an error.")
  }
  else
  {
    feResult = vTmp
  }
 

Hello,

Well since it is the holiday season, send your DB and DAT files to support@Lantica.com and I will have a look at it for you.

-Ray

Thanks. IT WORKS GREAT. 

Now I have another question. 
[email]The second one was that the XLookup is being done on two time fields.
Internally in Sesame a time is formatted as 02:30:00 but the element you were using as your key value was formatted as 02:30. What I did instead of changing your formatting was I added {+ ".."}, minus the braces, to the key value in the XLookup [/email]
I have two more time fields I will need to create a similar lookup....except the xlookup may not find an exact match so the next lower corresponding value needs to be assigned.  I thought the XlookupR would do it.  But it pulls in the next highest value.
Table Form (Source)

Time   Rating
1:15    50
1:30    60
1:45    70

Rating Form (Destination)

Time  Rating
1:39    60    (correct answer...XluR pulls in 70)

8)
I am so Happy!!!! I've learned so much working through this problem with your help.  This forum is SO valuable.

Happy Holidays!!!

Aren't these people GREAT!!!!