Changing member types

I ran into an interesting situation that RDi could have handled better, IMHO. I was developing an RPGLE program and then decided I needed some SQL in there. Since the verifier uses the member type to determine the allowable syntax I needed to change the member type. I used RDi to change the member type to SQLRPGLE.(Remote systems > Properties > Type).

The member was still open. When I tried to save it I received a message along the lines of the local copy not existing. It proceeded to create a new, empty RSExxxxxx member in the QRPGLESRC file - each time I clicked on save. The current program open in the editor did not get saved to those members.

To resolve the immediate issue I just reversed the change type process, saved the member, exited and reopened it. There are several resulting behaviors that could be improved here.

- Ideally the change member type function can check if the member is open in the editor and do whatever it needs to do to realign the work file.

- I could have been prompted to copy/save from the original work file.

It's not a showstopper, but I thought I'd post it in case some else decides to change member types mid-stream. And maybe the RDI development team will decide it's worth fixing/implementing.

-mark