Welcome! Log In Create A New Profile

Advanced

Table1.colonne..name = table2.colonne..name

Posted by Joao DE DEUS.pcs.crosspost 
Forum List Message List New Topic
Joao DE DEUS.pcs.crosspost
Table1.colonne..name = table2.colonne..name
July 10, 2009 11:42AM
Hello I think I detect a problem.

We used WD10 and we are upgrading projects in WD14. In a few projects i use tables with same column names. In wd10 i seek
tableseek(TABLE1.COLONNE_A..name,...) and tableseek(TABLE2.COLONNE_A..name,...) the program distinguished the columns.
But now it did not work anymore. I have to change the colum names.

Is it a bug or not?

Joao


Message forwarded from pcsoft.us.windev
Reply Quote
Fabrice Harari.pcs.crosspost
Re: Table1.colonne..name = table2.colonne..name
July 10, 2009 01:37PM
Hi Joao...

in each new version, the compiler becomes more strict and catches more
potential errors... This could certainly be construed as one, as
ambiguity and computing never mix very well

best regards

--
Fabrice Harari
International WinDev, WebDev and WinDev mobile Consulting

More information on [www.fabriceharari.com]


Joao DE DEUS wrote:
> Hello I think I detect a problem.
>
> We used WD10 and we are upgrading projects in WD14. In a few projects i use tables with same column names. In wd10 i seek
> tableseek(TABLE1.COLONNE_A..name,...) and tableseek(TABLE2.COLONNE_A..name,...) the program distinguished the columns.
> But now it did not work anymore. I have to change the colum names.
>
> Is it a bug or not?
>
> Joao
>
>
x
Message forwarded from pcsoft.us.windev
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: