I am working with a mature database that’s currently in v17.4. The primary input form relies on the Current Record. But I am pushing ORDA in - so I have a similar situation to you.
My solution is to maintain both, But very carefully. The form expects the current record of a table. The first thing I did was change the form from a Modify Record to a Dialog. All the old code still works. In this particular case there are a number of related tables to deal with. The old code did this using arrays and listboxes. It actually reads all the related records into arrays as it loads. The record has to be specifically set to READ/WRITE to edit it. And to save it deletes all the existing related records and uses ARRAY TO SELECTION to recreate them. I had never seen this scheme before. I get the idea but simply deleting and recreating all those records is just kind of sloppy.
So, to migrate to an ORDA form I have to work in steps. The first step is to begin populating FORM. So in the On load form event I look up the current record in the dataclass and put it in Form as Form.thisRecord. This is easy to do:
Using ORDA I can manipulate this at will. But that isn’t what the user expects. So I have to be careful not to change
thisRecord. But I can use it to begin to refactor the way the form deals with the related tables. And that’s what I’m doing listbox by listbox.
I have to stress how careful you need to be using this approach. I would not, for instance, attempt to change values in the Current Record by updating and save Form.thisRecord. With ORDA you can have multiple instances of a reference to the same record.