Generally speaking, it is a bad idea to make code changes to a live (production) database running in 4D Server that has users connected to it.

Ideally, code changes should be carried out on a development machine where the modifications can be tested before moving the updated structure in to production.

Making code changes to the production (live) database while users are connected can lead to unintended consequences and should be avoided.

For example, if there is a syntax error in an updated method, the users may be prompted with the syntax error that includes an option to either continue or abort. If they hit continue, what will happen with the rest of the method? Will it be Ok if the users just abort the method? Will their data be valid? Will they call you and report the problem? These are just a few questions that arise from making code changes to a productions database.