VBA code not contained in intended workbook

[pam53154]

We receive a monthly workbook from a service provider which has VBA code that prevents their users from inserting or deleting rows and columns. However, once we open the file it prevents us from inserting or deleting files in our separate workbooks. What type of code would cause these limitations to reach beyond the workbook with the code?

 

[6StringJazzer]

Very poorly written code. It may have something in it that is intended to operate on ThisWorkbook but instead uses ActiveWorkbook. However, it's very hard to diagnose without seeing the code. Is their VBA project password-protected?

You can always open the file without allowing macros to be run, although it may have traps in it that make you unable to work with the file if you do that.

If it were me I would complain to the service provider.

 

[pam53154]

Their VBA is password protected and they declined to provide the code when asked. They deny it is their code at all, although our issues are clearly traceable to having their file open in the background. They are allowing me to "look over the shoulder" of their VBA programmer while onsite next week. I know a bit about VBA but I am gathering some pointers so I can more quickly focus in on what could be the cause. We have complained profusely, but from what I can tell, their VBA developers lack the expertise to diagnose the issue.

 

[Norie]

Do you need this code?