> Are you sure that you fixed this? Looking at the settings window with 4bb6243 I still cannot change the settings window nor is the line wrap for longer text visible. The screenshot above is the same I see just now.
I hear you @Hosch250 when you made suggestions about too little/too much info in the issues. Might put my Aussie pennies on the table here as place a issue ticket to @Mat'sMug suggestion box about setting up a formal issue template see github.com/blog/2111-issue-and-pull-request-templates for ensuring consistent information from
users and/developers as you have two kind of demographic groups
A little while ago, we issued an alpha release of Rubberduck 2.0, just because, well, v1.4.3 had been around since July 2015, and we wanted to say “look, this is what we’ve been working on; it’s not nearly stable yet, but we still want to show you what’s coming”. Time flies. 6 whole weeks, 353 commits […]
Im trying to make a calculator in vba in access but I don't know how to make the "=" button in the calculator, I press a number like "2" AND when I hit the "+" I made a variable hold the number in memory like "a", so a = 2, then the calculator cleans the text box and accepts a second number that ...
> If VBE settings are set to *Require Variable Declaration* then `Option Explicit` is added to all new modules. If Option Explicit is missing, then the module is inspected, but if Option Explicit is present (maybe as a result of a prior inspection fix), then there aren't any inspections that notify the user of an otherwise empty module.
If a user adds modules but fails to add code, or a user removes/refactors code out of a module, they can end up with otherwise empty *and* unused modules. Tha
@PeterMTaylor beta should install fine, but your debug build will then need re registration... better to just keep the debug build if you want to keep up! ;-)
Being new to coding and slow in understanding sorting methods such as "bubble sorting" and others, I tried to invent something easier to solve the sorting problem by making new Collection. I transfer items from old Collection comparing them to the new Collection. I don't know how to compare it wi...
@Vogel612 I saw that in the logs. It did seem strange. Like, *surely* the parser breaking on Option Explicit is something that would've been noticed before now?
I'm new to VBA and currently trying to accomplish a simple task:
There are two worksheets with the used Range("E2:G7").
For each value greater 4 in worksheet(1) I want to colour the corresponding cell in worksheet(2).
Sub Button1_Click()
Dim Zelle As Range
For Each Cell In Tabelle1.Ran...
@Raito start with specifying Option Explicit at the top of the module, I noticed you're using undeclared variables. also Cell would be an ambiguous identifier to use for this.
Sub Button1_Click()
Dim Zelle As Range
For Each Zelle In Tabelle1.Range("E2:G7")
If Zelle.Value > "4" Then
Tabelle2.Cell.Interior.ColorIndex = 3
Else: Tabelle2.Cell.Interior.ColorIndex = 8
End If
Next
End Sub
@Mat'sMug Actually I am using Zelle as identifier, just tried translating it. Bad idea, I guess. Yep, two sheets. If you click the button on Sheet1 it's supposed to mark entries in the same cell on Sheet2. As long as I work within one sheet it works. How would I loop through the two sheets so the cells are "the same"?
If Zelle.Value > "4" Then
[Worksheet2].Cells(Zelle.Row,Zelle.Column).Interior.ColorIndex = 3
Else: [Worksheet2].Cells(Zelle.Row,Zelle.Column).Interior.ColorIndex = 3
which you can then do like so Set [Zelle2] = [Worksheet2].Cells(Zelle.Row,Zelle.Column) If Zelle.Value > "4" Then Zelle2.Interior.ColorIndex = 3 Else: Zelle2.Interior.ColorIndex = 3
@Raito Aye. Recently I got to see THE spreadsheet that runs a huge international Conglomerate. Its' full of figures like "European Sales - Region 1 - £2,617" (Million). It's got over a hundred sheets. And the VBA behind it is Awful.
@Hosch250 aye - SC should send a message to App saying "look, I'm about to export and re-import a bunch of modules, just switch off your sink handlers and let me handle this okay?"
> RD sets the state to resolving after a parser error. Then, it gets stuck at resolving because it isn't really resolving, and we can't bring the parser error window up...
> (Anecdotally) Only seems to occur when I've already had a project open. Not all the time, but once it's been triggered once, will reliably trigger for every opening of a workbook thereafter.
I'm new to VBA and currently trying to accomplish a simple task:
There are two worksheets with the used Range("E2:G7").
For each value greater 4 in worksheet(1) I want to colour the corresponding cell in worksheet(2).
Sub Button1_Click()
Dim Zelle As Range
For Each Cell In Tabelle1.Ran...
VBA Rubberducking
VBA Rubberducking