Hello there again,

since the last post, I have figured out some way how to avoid major issues but it still doesn't solve the problem in general. It is possible to avoid that mistake by built-in "Reset" function in the SP editor. After clicking it we are using every previous setting like in the attachment (solution_nr1). After such a move everything seems to work correctly until it going to happen again. However, this method works every time when I've tried so even if will be necessary to Reset the SP really frequently it is possible to continue typing the script.

Still fetching the right solution

I have been working on 3 diffrent version of Allplan one of them is 2021-0-3. I have also tried 2023.

I did not try.

Unfortunatelly I cannot attach the file, I know that could help. Inside the script are only really simple function such a loops, conditions, dim variable and that is it. Nothing more, there is no any fancy fucntion which connecting two different SP files or something like that.

Hi,

I know but I am obligated to not reveal the code. I was not copying and pasting anything, this code has been written by me entirely from scratch. So if somehow something has been implemented into my script (maybe one day I have pasted something but I do not remember this) I do not know about this. Now this is causing that issue, puzzles me, why the SP editor debugger does not catch that error.
Should be like any unknown character stops the script, should not it?
Sometimes when I am testing is like everything is working, I am typing in the variables, and moving the handles, and then is that moment when I writing in one line of code or I am adding one parameter (sometimes I am creating a new parameter and script is not working but when I do even small correction in name of the parameter then is working) and the script stops.
So, I am wondering how it is even possible that that script is working to some point and then stops.

When I read what I typed here I am not sure that will be understandable. However, there are so many small weird errors inside that SP that is so hard for me to explain when they occur. I will try to prepare a more extensive explanation of this when I would have more time for it.

Best regards.