Thanks for not deleting it, Marijan.
I think many of us have been in a similar situation only to realize what you realized after spending a long time trying to make sense of it.
In most cases, this is as you wrote, caused by a variable having the same name as a table or column.
Cheers
Peter
From: mapi...@googlegroups.com <mapi...@googlegroups.com>
On Behalf Of Marijan
Sent: 2. april 2025 21:41
To: MapInfo-L <mapi...@googlegroups.com>
Subject: [MI-L] Re: Expression does not evaluate to a column or table name error
This message originated Externally. Use proper judgement and caution with attachments, links, or responses. |
I was about to delete this question but I decided to leave it for future me, or anyone else. Problem was that I defined variable with same name as mentioned column. Even after commenting bottom part of code, declaration stayed at header.
--
--
You received this message because you are subscribed to the
Google Groups "MapInfo-L" group.To post a message to this group, send
email to mapi...@googlegroups.com
To unsubscribe from this group, go to:
http://groups.google.com/group/mapinfo-l/subscribe?hl=en
For more options, information and links to MapInfo resources (searching
archives, feature requests, to visit our Wiki, visit the Welcome page at
http://groups.google.com/group/mapinfo-l?hl=en
---
You received this message because you are subscribed to the Google Groups "MapInfo-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
mapinfo-l+...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/mapinfo-l/aac9b0e3-3047-4be4-ac22-5c699a05bb33n%40googlegroups.com.