> Thanks for the report! Note that discarding of the return value would potentially be a problem at the function's call sites, not in the function itself. Hence the inspection is reporting usages of the function, unless the return value is being discarded at every single call site, then the function itself is being flagged.
Given the above, this code should trigger the inspection:
```vb Credentials user, pwd ```
And this wouldn't:
```vb Dim creds As Dictionary Set creds = Credentials(user, p
> I think what might happen here is that the references to the function return value itself inside the function trigger the inspection, which is a bug.
Generally, any method access should be ignored by the inspection. However, I think the code used to identify such cases is not quite right.
> There are multiple reasons why the code explorer does not show locked projects.
Currently, the code explorer works exclusively off declarations parsed from the user code. Since there is no access to the code in locked projects, these are not shown.
For some time, we can actually see the structure of locked projects through some trickery.; the code is still not accessible. So, in principle, we could show the structure of locked projects, with the obvious restriction that there could not b
> If the locked structure would be displayed and you could then unlock the projects with the Code Explorer, i.e. the Code Explorer would offer the possibility to enter the password, it would make sense from my point of view.
> Hello again. Just wanted to say that the currently latest version works really well with CorelDRAW. Of course, indentation works, as previously. Code inspections work and I have cleaned up a lot of code thanks to them. Code metrics work, Code explorer works. Autocompletion works. Need to learn more about the functions in general to use them more often.
Also, in the latest version the insane slowdown mostly goes away if "Run inspections on successful parse" is disabled. So thanks a lot for
The following code works perfectly. It just works very slowly. Is there any way to speed up/optimize this code?
I think its the amount of loops but I am unable to figure out how to reduce the number of loops without hampering the functionality of the code.
'''
Sub inland()
Dim sort As Worksheet
...
I am far from a REST API expert, however, thanks to help from the wonderful people here, I've managed to execute a few calls to our 3rd party calendar provider to get data from them. It works so much better than scraping their website!
However, I've noticed some issues with oddball characters coming back in the unicode strings they're returning that my SQL Server doesn't like ingesting.
Their support is working on identifying and resolving the issues, however, in the meantime, they've indicated that I can request only the fields that I'm interested in (excluding things like "notes" that have, in the past included these weird characters), and have pointed me to their documentation in order to determine how to request just the fields I'm after.
However, it seems my understanding of REST API documentation is still not complete, as I can see no place in their documentation that tells me how to tell them which columns I want in-/ex-cluded from their response.
Would any of the kind souls here be willing to peruse the docs to point out what I'm obviously missing (since they said the info was there)?
DbRecordset is a new class added to a fork of the SecureADODB library, which wraps the ADODB.Recordset class. It complements the functionality of the DbParameters class from the previous post and focuses on updatable recordsets. IDbRecordset class formalizes its public interface providing methods...
@FreeMan, I'm just curious. What are the weird characters?
Of note, your API let's you define a character encoding. It defaults to UTF8, the characters you are seeing might be a mismatch between source and destination encodings. If you can't handle UTF8 then change the encoding received.
encoding string
If using the XML response_type, use this to change the character encoding of the XML response; valid values are any valid character encoding
> Hi there, very glad to hear about a happy ending here! Note that you can group (and filter) inspection results in several ways (by inspection/type/severity, ...and by module) using the various knobs & buttons toolbar at the top of the inspection results toolwindow. Cheers!
On Tue., Sep. 14, 2021, 06:38 Clemens Lieb, ***@***.***> wrote:
> Closed #5656 <https://github.com/rubberduck-vba/Rubberduck/issues/5656>. > > — > You are receiving this because you commented. > Reply to this email directl
> Yep, that's a bug! This one's on us, but as a rule of thumb (perhaps a stylistic choice) I would systematically avoid treating a function's return value as a local variable like this, and declare an explicit local instead; that makes the function's identifier name only appear LHS of an assignment in the case of the return value assignment (or, more rarely, in the case of a recursive call), which Rubberduck should parse and analyze correctly every time.
I miss y'all so much! Rubberduck isn't dead, but I've (predictably) burned out and needed to take some time away (not just from RD) for a while. I'm sorry I've let you (and our users & fans) down and in the dark, I'm alive & well and will be resuming RD and blogging as soon as some renovations here get finished and my home office is set up - couple of weeks, should be ok for Hacktoberfest =)
It's OK, @MathieuGuindon, everyone deserves a little time off. Now, ComIntern, he's taken far too much time off!!! (Anyone hear anything from him since he announced he'd be gone for a bit?)
@HackSlash It's been a few weeks, I don't specifically what it was, but it was in a [CDATA] section of a <Note>. I do not need notes, so if I can figure out how to not get them sent to me that would be ideal. Heck, I don't even read them in the Stored Proc that loads the data for me, it's just that SQL Server saw it in the XML stream and decided to barf.
There was also something late last week that tripped me up, but there was nothing in the least bit obvious about what was wrong. it was a <tag>[CDATA]TEXT STRING</tag> and feeding it through a unicode decoder revealed absolutely nothing in the lesat bit odd about it.
VBA Rubberducking
VBA Rubberducking