Hi
I have this "finished" db. I prevent the use of shift and convert it to acdde.
I Know that there is no viewable VBA code after the acdde conversion and you can't reach the VBA editor because of the disabled shift.
Nevertheless I put a password for my VBA code (so if there is another way to reach the editor (other than shift) to not be able to see the names of my forms and modules)
I added a last minute piece of code that includes some checks and in some conditions the renaming of a form. (with DoCmd.Rename ...)
I get an [Error 2017] that my code is protected. I guess it's normal behavior, although I found it weird somehow to not be able the same (protected) code to change the name of a form.
Is there any workaround on this?
An error handling or something, so that the form to be renamed and to have a pass for the vba editor?
I have this "finished" db. I prevent the use of shift and convert it to acdde.
I Know that there is no viewable VBA code after the acdde conversion and you can't reach the VBA editor because of the disabled shift.
Nevertheless I put a password for my VBA code (so if there is another way to reach the editor (other than shift) to not be able to see the names of my forms and modules)
I added a last minute piece of code that includes some checks and in some conditions the renaming of a form. (with DoCmd.Rename ...)
I get an [Error 2017] that my code is protected. I guess it's normal behavior, although I found it weird somehow to not be able the same (protected) code to change the name of a form.
Is there any workaround on this?
An error handling or something, so that the form to be renamed and to have a pass for the vba editor?