axlDBCreateVia

Here are a couple of things I've tried:
1) Add a small shape (size of via pad or smaller) with the proper net at the via location. I also fix the via and put a comment on it "stiching via". Downside is if you need to move it, you have to remember to move both the via and the shape.
or
2) Create a single pin part in the schematic for a stiching via with a physical symbol that has a pin the size of a via. Downside is you have to put them in the schematic and you might have some issues if your spacing rules are different for pins vs. vias.

What you suggested is a workaround but not very convenient.

In fact I have other vias that have the same goal (interconnect all shapes of the same net) that are connected and stay connected. So this way to put vias is "allowed". If I copy one these connected vias, the new one will be connected (if I check the "Retain net of vias" in Options tab.
So, these "already connected" vias and copies always stay connected whatever I do.

Only vias created by skill lose the connection. So I think that there is something to do bu Skill.

I tried to select vias when one of the shapes is visible (by default negative planes are not displayed).
But it has the same result: vias came back to unconnected.

Then I tried to slide one these "stupid" via and put it back to ix 0 0.
In this case, when all others came back to unconnected, the "slided" one stay connected to the wanted net!
So I can add skill code to slide each via but it will be the last solution... jut before adding small piece of shapes.. ;-)

Thanks for reply.

the same via has 3 different dbid number:

unconnected via dbid:117964928
the connected via dbid:135767588
the via after a dbdoctor dbid:135768336

It is clear that the first and the second one are different (via delete and via creation) but the second and third should be the same!

solved.

I like SKILL language but I hate its strange behaviour sometimes...

It was due to the code:

previous code:
Select the via, create a new one using oldvia->name and oldvia->xy then delete the oldvia.
this does not work. In fact it works but the via does not stay connected.

New code:
extract the via. store xy and name in variables, delete the via, then create a new one using variables.
This works perfectly...

If somebody can explain this... I like rational explanations ;-)

The problem you had makes sense:

1. When creating a new via at the same xy, the existing (floating) via connects to your new via.
2. Next, when you delete the original via, any connected objects need to be updated. (your new via)
3. Since there is no other connected object to keep the new via on the desired net, the new via becomes floating when the update occurs.

Here is a speed tip when re-creating objects:
   Save the data for the new objects in a single variable.
   Delete the original objects if needed.
   Create a single procedure to create objects; pass in all the data using the one variable
   Use axlDBCloak on the call to create the objects
   (only add the axlDBCloak when you know the code works, it has error catching and will not show any errors if they occur which will make it difficult to debug)