Updating to 2.1 and now begin again... and worse when copying and pasting Xojo crashed (and not always)
Now change all IN/OUT code again.....

where

row.BooleanColumn("Advance") = u.Advance

now is

row.Column("Advance").BooleanValue = u.Advance

and so on

hundread os code lines to change..

Var row As New DatabaseRow

row.BooleanColumn("Advance") = u.Advance
row.IntegerColumn("atack") = u.Atack
row.IntegerColumn("CounterCol") = u.CounterCol
row.BooleanColumn("Exchange") = u.Exchange
row.BooleanColumn("Exited") = u.Exited
row.IntegerColumn("ID") = u.ID
row.BooleanColumn("IsAttacking") = u.isAttacking
row.BooleanColumn("IsDead") = u.isDead
row.BooleanColumn("IsTarget") = u.isTarget
row.IntegerColumn("Left") = u.Left
row.BooleanColumn("Moved") = u.Moved
row.IntegerColumn("Movement") = u.Movement
row.BooleanColumn("MustAttack") = u.MustAttack
row.BooleanColumn("MustBeAttacked") = u.MustBeAttacked
row.Column("name") = u.name
row.Column("Nation") = u.Nation
row.IntegerColumn("offsetLeft") = u.offsetLeft
row.IntegerColumn("offsetTop") = u.offsetTop
row.Column("OldPlace") = u.OldPlace
row.Column("Place") = u.Place
row.Column("Reinforcement") = u.Reinforcement
row.BooleanColumn("Selected") = u.Selected
row.IntegerColumn("Side") = u.Side
row.Column("tipus") = u.tipus
row.IntegerColumn("Top") = u.Top

etc.etc.

Is this your only copy of the code?

Assuming not ..Doesnt an earlier build have the coding method you want to switch back to?
Arbed editor can identify the differences and update/revert with a mouseclick.

Doesnt an earlier build have the coding method you want to switch back to?

My code has been changing, probably the latest version before 2.0 is not up to date, so I should check every methods and line where DatabaseRow is involved either way.

Before making a such change Xojo team should have found a better solution.

Greg, with 2.1 if I do not upgrade the code it won't compile... or you are suggesting to keep the 2.0?

Tobias, reverting to DatabaseRecord (This item was deprecated in version 2019r2. Please use DatabaseRow as a replacement) has its consequences, is perhaps less work that changing all code lines, but I keep using obsolete code, until …?
Release 2.0 was a mistake but now I'm inside it and it's complicated to go back.

Thanks Dave, is exactly what I realize I should do, now that I left the anger and I'm accepting the fact.

I already save-as all current projects, and worked in them so, I must be patient, revert what is necessary and accept r2.1 is the version to follow.

a. staying with API 1 ?
Every now and then, I made a copy in the Finder, into a backup projects folder of the current state and I append the date to it for future reference(s).
This seems, IMHO, a good idea with API 2.

b. Changing Xojo to a new version ?
IMHO and if you can do that (there is n workaround you are waiting for in a new version): always stay with the actual Xojo version until the project is done. You will upgrade before you start another project. Two “good reasons” (also IMHO):
a. this keeps you away of bad things that can appears sometimes after a new version is released (we alread saw that in the past; this is not a rant, just something that can happens, sometimes, rarely).
b. even if the new release does not have troubles, you may reach slowdown because of changes (even good changes): we most of the time have to ‘waste’ time to adapt to the new version and if you have a project running (/ near the release time), you cannot slow down the development.

As usual, this is my opinion, do what you want, what you know is better for you.

Regards.

I have had the bad habit to update very soon and look at the news and use them, now I'll be more patient... for example Catalina is there and I have no intention to change for now.

Enric: I understand, but with ellapsed years (I’m in my 60s), I became prudent (I am still curious for everything, but I refrain myself on some domains). ;)