Hi
After installation of the Last Stable Version of Elements, the following methods calling, doesn’t work anymore
method Engine.init;
begin
const Test;
method initializeDataBase;
begin
result:= false;
…
…
…
end;
try
if (not initializeDataBase) then begin
exit;
end;
except
Log('-> ***** Fail *****');
end;
end;
When hit if (not initializeDataBase) then begin, it breaks to Except directly
In the last stable version, we haven’t noticed this behavior
Version: Visual Studio 2019 and 2022
Elements: RemObjects Elements with Water - 12.0.0.3025.exe
Data Abstract: RemObjects Data Abstract for Water and Visual Studio, Server Edition - 10.0.0.1621.exe
mh
November 7, 2025, 1:11pm
2
What platform is this, .NET?
mh
November 7, 2025, 1:15pm
4
I had to make a few changs for you code to compile, but it then works fine and as expected:
what could i be missing?
We can’t do the changes, the methods had dependent variables, it was working in the release before
This snippet sent, was just an example
When consuming objects that has been created inside “initializeDataBase“ in the current init flow, it give us an error.
Thx
mh
November 7, 2025, 1:44pm
6
Anderson_Gregorio:
We can’t do the changes, the methods had dependent variables, it was working in the release before
This snippet sent, was just an example
When consuming objects that has been created inside “initializeDataBase“ in the current init flow, it give us an error.
Well, i need an example that compiles and shows the problem, for this to be actionable. In your example, the next method had no return type, so you couldn’t assign a result. Once i added it, it compiled and worked as expected. Also, the “const Test;” had no value, and was an invalid declaration…
I also see no issues accessing objects created inside the nested method, as per below:
I’m really afraid I’ll need something more concrete to reproduce what may be going wrong for you, and to diagnose whether what you’re seeing is a compiler bug or “correct”/expected behavior for incorrect code.
Hi, I couldn’t replicate the bug, but reinstalled this version and the project has compiled and executed as expected.
I’m working to findout what couldt it be.
Thx.
Hi
We fixed the problem, may be related to new configs in our environment
No problem anymore.
Thx
mh
November 12, 2025, 11:01am
10
Happy top hear you got it sorted!
That said, if theres even a chance that you thionk this was caused by an compiler change, i’d still love to fingure out what was going on…
