> Just installed the hotfix (x86 versions) and tested it and I am no longer having any issues with the Test Explorer and protected modules. Thanks for the rapid fix!
> When running the Code Inspections, I have found that it doesn't consistently report that a variable is never used - sometimes it will report a variable as never used, other times it won't. I have an ErrorLog function that contains the following code: Dim iFileNumber As Integer ' Create the error text to be logged. sLogMessage = sErrorLocation & ", Error " & CStr(lErrNumber) & ": " & sErrMessage iFileNumber = FreeFile() Open sPath & msLOG_FILENAME For Append As #iFileNumber 'Output time and...
message to log file. Print #iFileNumber, Format$(Now(), "mm/dd/yy hh:mm:ss") & " " & sLogMessage Close #iFileNumber To me, I would say that the variable iFileNumber is used (a number of times at that). When I run the code inspections, sometimes it reports this variable as not being used, and other times it doesn't. !codeinspection1...
!codeinspection2 As can be seen in these two screenshots, the second one contains an additional two issues - for "Variable 'iFileNumber' is never used" (two because I have similar code in another function). I did nothing to the code between taking these screenshots - all I did was press the refresh button in the Code Inspections window. After pressing the refresh button another three times I...
got the same code inspection results as in the first image. This appears to be not very consistent in terms of reporting issues with the code. System details: Windows 7 (64-bit), with Excel 2010 (32-bit) running Rubberduck 1.22.55668.31692 (32-bit)
> Possible duplicate of #282 and #260. We've been struggling with this one. @retailcoder has been working on an improved grammar and parser for the next major release.
> That's a new one... and a scary one at that. I'll keep an eye on it, but the identifier usage inspector no longer exists in my build, replaced with much simpler code, although I'm seeing the false positives... #ParsingIsHard #GrammarIsFun
Ugh. New phone is about to learn that I write what I write and if you don't let me then your smart as autocomplete/autocorrect feature is going out the window
How can I programmatically determine the current setting for Option Base in VBA? The Option Base can be set to 0 or 1, and this determines whether array indices start at 0 or 1 (see MSDN).
However, I can't see any easy way to find out what the current setting is. I was hoping there might be an O...
Well technically the Rubberduck inspection does find Option Base 1 - only the quick fix for removing it isn't implemented for the reasons described in the GitHub issue you linked to ;) — Mat's Mug2 mins ago
I had a single which I believe the C++ equivalent is float in VBA in an Excel workbook module. Anyways, the value I originally assigned (876.34497) is rounded off to 876.345 in the Immediate Window, and Watch, and hover tooltip when I set a breakpoint on the VBA. However, if I pass this Single ...
Over here for data entry people, they take whole spreadsheets full of data rows, print it onto a really big sheet of paper, then enter it row by row and mark completed rows with a highlighter.
I was gonna say, if you get the information into Excel, you can write SQL queries as Excel formulas using the data in the cells and then copy the formula to the whole sheet
Then copy that and paste as data into another sheet, copy paste into SSMS and boom
="SELECT Sequence_Number FROM dbo.STAR_Products WHERE Contract_Number = '" & A2 & "' AND Sequence_Number ='" & G2 & "' UNION"
(I actually used that trick a few times for Cardshifter when we stored the card data in Java - Simon gave me a weird look, needless to say ;)
I had a single which I believe the C++ equivalent is float in VBA in an Excel workbook module. Anyways, the value I originally assigned (876.34497) is rounded off to 876.345 in the Immediate Window, and Watch, and hover tooltip when I set a breakpoint on the VBA. However, if I pass this Single ...
VBA Rubberducking
VBA Rubberducking