J
James Palmer
Guest
So I've been trying to get proparse working on my code base, and one of the issues I've come across that really messes with it is something I would consider to be a cause for throwing a compile error, but doesn't. Before raising it with support I wanted to check I'm not missing something. Against sports2000 consider the following: PROCEDURE DoesThisWOrk: define input parameter ipBinName like sports2000.Bin.BinName. end. This is absolutely fine. But if I change the table name as follows it still compiles: PROCEDURE DoesThisWOrk: define input parameter ipBinName like sports2000.WhateverTheHellIWant.BinName. end. This is because BinName is a unique field in the database and therefore the compiler can resolve the field properly. Interestingly if you remove the DBName from it it throws an error on compile. We've got a few cases where someone in a rush has fallen foul of this because most of our fields (except keys) are uniquely named and thus the compiler can resolve what you mean. But understandably proparse throws a right wobbly because it can't find the table in the schema. Is this a compiler bug? Is it worth raising it with support?
Continue reading...
Continue reading...