I'd go with Access.

Haven't seen anything on that. It's not on the @(local variable) page that I see.

Then again, I don't think it's a good idea. Just an interesting question

Not sure where sysname comes in here with "all variables", but am I missing something?

Glad you found it. I know that can be maddening.

I have no idea why proc fails and sql works. That's why I asked to check versions. I have had versions seem to rev underneath me. Building a second proc...

@jason

I do think EAV has a place, especially in the real world. We don't live in a perfect world, especially with regard to requirements/specifications and time. We do...

@Carlo P - I think my handling tends to be more consistent where if you have translations, you're a) putting one language ahead of others and b) means I need...

Something seems odd. Are you sure you have the same version of the proc code?

Maybe try this:
- Script the proc out
- change to a new name...

This might help: http://www.sqlservercentral.com/blogs/sqlrnnr/2018/11/26/ghosts-in-your-database/

I don't think this is parameters. Looking there likely is a distraction. I suspect there's a data error somewhere in a table, and I'm guessing that's where the issue is....

I don't see EAV as evil. They don't scale well and they can be problematic for busy workloads, but for an ad hoc item that you don't want to put...