OK, thank you. I see that many of them are because Q&A can use nested Xlookups but I need to put each one on it's own line in Sesame. Not a problem, just a lot of work. Oh well, job security.
Here's one that has me stumped, however. This works in Q&A:
>#2175:IF #2005="" THEN {IF NOT #2050="" THEN {{if not #2076="0" then
#2005=@STR(#2076)+" "+@STR(#2025)+" "+@STR(#2050)
else #2005=@STR(#2025)+"
"+@STR(#2050)};if not #2075="" then #2005=@str(#2005)+" "+"SN"+@str(#2075)};if #2005="." then #2005="";
if (#2100+#2101+#2125+#2126+#2150+#2151+#2175)>"0" then goto #2176}
ELSE GOTO #2200
After translation (and a bit of cleanup) it looks like this:
IF F0008=""
THEN
{
IF NOT MODEL1="" THEN
{
{
IF NOT NO_OF_PIECES1="0"
THEN F0008=@STR(NO_OF_PIECES1)+" "+@STR(MAKE1)+" "+@STR(MODEL1)
ELSE F0008=@STR(MAKE1)+" "+@STR(MODEL1)
}
IF NOT SERIAL1=""
THEN F0008=@STR(F0008)+" "+"SN "+@STR(SERIAL1)
}
IF F0008="."
THEN F0008=""
IF (LENGTH_FEET1+LENGTH_INCHES1+WIDTH_FEET1+WIDTH_INCHES1+HEIGHT_FEET1+HEIGHT_INCHES1+WEIGHT1)>"0"
THEN GOTO F0123
}
ELSE GOTO ONLY_MACHINE
The program editor is choking on line 6, the third nested { (the editor says it's expecting } ).
Please don't anyone spend any extra time looking at this, as I'll probably re-write it all anyway using variables. But if anyone can quickly spot what's wrong with my nested brackets I'd appreciate the information.