VBA Code Works For All But One

[roxorvoxor]

I have a workbook that has been in practice for 2 years. It uses VBA code to find the intersect of two values in a range and enters an X. This has worked flawlessly since inception... until today. A user approached me as they were getting an error that they were trying to change a protected workbook. The workbook is protected but the range is unlocked. After fiddling around (I couldn't replicate on my own workstation) I unprotected the workbook and had him enter again. I noticed that the intersect did not enter in the range. It entered it in a cell directly across the input cell. I had other users test it on their workstations and no one else had an issue; it intersected as expected... dang that sounded good. Anywho, has anyone seen anything like this? I had him close everything out, reopen, restart his computer, and even delete his Excel cache. Still no go.

 

[StephenCrump]

The description is a little vague. We'd need to see your code to understand what it's doing, and what might be going wrong.

But my first guess is that:

- Your code is relying on the position of ActiveCell, and assuming that the user made an entry in the input cell above.
- The one user has different settings, e.g. perhaps Application.MoveAfterReturn = False.