Actually, this would not be a good idea to do in the first place.
There are formal rules of Database Normalization which describe how tables and the relationships between those tables should be designed.
I strongly recommend you put further work on this aside and invest time in learning those Database Normalization rules so you can correct the design flaw here.
Because we don't really have any context for this particular table, and can only assume from the terms used that it has something to do with Stock investments, it would be premature to suggest a revision of the table at this point. That said, we can identify and address the specific flaw.
One of the fundamental principles of good relational table design is that each data point is stored once, in one field, in one table. Therefore, copying a value from a field called "Stoplevel" to a field called "Closed" is an invalid design. In order to help you correct it one would need to know more about the intent underlying the database.
Search the internet for discussions of "Database Normalization".
Here's one for starters. https://learn.microsoft.com/en-us/troubleshoot/microsoft-365-apps/access/database-normalization-description
I also like the series of YouTube videos from this channel. Although they are as not technically complex as they could be, they do explain enough about the concepts involved to help beginners get started.
https://youtu.be/GFQaEYEc8_8?si=to9NUSJgKYrIwsmm