syntax error

[daN baueR]

Problem Solved

Variable x changed to xx, which avoided the conflict with associated
group X. Thanks for your assistance. This one was very painful.

Dan

On Thu, Apr 7, 2011 at 10:03 AM, daN baueR <onlinemgt at gmail.com> wrote:
> Top post
> Yes this error appears after I respond y to check syntax. Both lines of code were tried at different times while I attempted to debug this table. I'll check for ASSOC field X.
>
> Dan
>
> Sent using a personal electronic communications device.  Please excuse the brevity of this message and erratic spelling/typing.
>
>
> On Apr 7, 2011, at 9:53 AM, Kenneth Brody <kenbrody at spamcop.net> wrote:
>
>> On 4/6/2011 7:54 PM, daN baueR wrote:
>>> On Wed, Apr 6, 2011 at 6:14 PM, Kenneth Brody<kenbrody at spamcop.net>  wrote:
>>>> On 4/6/2011 5:38 PM, daN baueR wrote:
>> [...]
>>>>> Could someone please point out my syntax error here.
>>>>
>>>> I don't see one.  What does the error message say?
>> [...]
>>
>>> *** A filePro Error Has Occurred ***─────────────────────┘ -   -   -   -   -
>>>        ◄ If:                                                                   ◄
>>> Line Number: 82                                                                ◄
>>> 101  -------   -   -   -   Check Syntax? (Y/N) Y   -   -   -   -   -   -   -
>>> a=this(x); that(x)=a                                                           ◄
>>>        Th^n:                                                                   ◄
>>> Process contains a syntax error at position indicated. -   -   -   -   -   -
>>>        ◄ If:                                                                   ◄
>>>        Then:                                                                   ◄
>>> 103  -------   -   -   -   -   -   -   -   -
>>>
>>>
>>> This is the actual report that I get when I try to test the syntax.
>>> It's bit scrambled but this is the new code that I'm trying to add so
>>> I figure this is it. And this the section of code that pops up after I
>>> press enter.  I'm remote now so this is the best I can do for term
>>> emulation. I think it's pointing to the (x)
>>
>> Okay.
>>
>> First, it appears that this is happening in *cabe, not at runtime, correct?  (You failed to mention that before.)
>>
>> Second, it appears to say that the error is on line 82, and that the line says:
>>
>>    a=this(x); that(x)=a
>>
>> with the caret pointing to the semicolon.  This does not match the code that you previously posted as line 82:
>>
>>    that(x)=this(x)
>>
>> Which one is it?
>>
>>
>> Finally, and this is just a guess...  Do you have an associated field group "X"?
>>
>>
>> --
>> Kenneth Brody
>