> First I just want to say that Rubberduck has been _extremely_ helpful to me as I have inherited a number of Access applications. I am new to coding in general and both the Rubberduck add-in and the blog posts have been great guides as I have been working on the applications over the last 7 months. Thank you all for the work you put into this project!

One of these Access .accdb files is giving me a Resolver Error when I try to refresh Rubberduck.
![image](https://user-images.githubuserconte

> Seems like there is some form of addition in a place where we expect a Type. The stacktrace of the resolver error suggests the `Implements` definition in one of these modules contains an unexpected `+` or `-`:

```
System.NotSupportedException: Unexpected context type Rubberduck.Parsing.Grammar.VBAParser+AddOpContext
at Rubberduck.Parsing.Binding.TypeBindingContext.BuildTree(Declaration module, Declaration parent, IParseTree expression, IBoundExpression withBlockVariable, StatementResol

> Thanks for the quick response!

There are two Implements statements in the entire project
I'm working on improving this, but like I said I'm still pretty new at this :)
Neither of the Implements statements are in the modules of the Reports that I mentioned above.
Let me know if you'd like me to share more information about where these two Implements statements are used.

If I remove all, but one of the report modules causing the issue then this is the only code in that report module.
`

> Thanks for the details. I think I have an idea what the problem is.

We use the VBE's internal type library for the project to get the supertypes of document objects. What our process does not seem to be prepared for is that the names of these supertypes do not have to conform to the usual restrictions imposed in VBA code.

I think the info provided will help a long way to reproduce the issue.

Add test cases for creating Let/Set properties

Adds MCVE tests for parameter list bug. Scenarios: 'Property Let' prototype used to create a 'Property Set' member and 'Property Set' prototype used to create a 'Property Let' member.

Fix parameter list bug for Let/Set prototypes

Fixes parameter list bug for scenarios where: 'Property Let' prototype is used to create a 'Property Set' member or a 'Property Set' prototype is used to create a 'Property Let' member.

Merge pull request #6049 from BZngr/SetFromLetCodeBuilder

Fix CodeBuilder create Let/Set code block issue