Duh check: There's no difference in the postfix decrement for (int i = bottleCount; i > 0; i--) and prefix increment for (int i = bottleCount; i > 0; --i) is there?
> The result of x++ or x-- is the value of x before the operation, whereas the result of ++x or --x is the value of x after the operation. In either case, x itself has the same value after the operation.
> Of course it is (looks cheap) It was a "quick-and-dirty" job, I needed it a month ago, so I just came with something that will do the job in minimum effort. This is why I am shifting this to you guys. If you want I can send also the VBA code used.
@Duga @ShaiRado lol, I didn't mean to criticize the UI ("looks cheap") - my comment was more aimed at the functionality itself; just a thought about it making it possible to [mis]use it as some kind of source/version control tool, which would be a shame given proper git source control is right there, two clicks away =)
doesn't matter if it's not "done right" - just have a SQL Server instance setup, and move the data over there. it can always be "made right" when you learn more about SQL Server.
(not without some pain alas)
but 700MB Excel files is definitely a sign
rule of thumb: if your Excel workbook doesn't fit a CD-RW, it's probably too large.
Who has a workbook that large? I dont even know how (unless every cell has formatting, even if it isnt used, and there are hundreds of sheets with formatting but no data).
For learning C# in VS. Do I want just an Empty Project? I've works with WF and WPF but I dont imagine those being very applicable for general C# programming.
Yeah, i've tried learning .Net before using WPF and Winforms for VB.NET but it is far more difficult to write basic programs that way (at least for what I do) so I never get to spend enough time learning. I just go back to VBA
yeah.. best start with a console application and learn how events (/delegates) work in .net before you start whipping up a form and writing click handlers
don't get me wrong: you can definitely double-click a button in the designer and do pretty much exactly as you would in a VBA UserForm... it's just not a good way to learn things IMO
Don't you just love it when an anonymous utility function you copied off the internet 2 years ago that has worked flawlessly ever since suddenly starts throwing 1004 errors for no discernable reason.
I've filed this one under: "I have no idea. Do it manually this 1 time. If it happens again, let me know".
It was an example for @puzzlepiece87 and I was going off some sample code he provided. I didn't know what was started in the with block and he seemed to understand my explanation.
If there's something that prevents me from doing it I'm unlikely to do so. At least not before I educate myself to a level where I'd be comfortable doing so.
@Mat'sMug As promised, here is the link to the repo with my VBA stuff that has some roots in your VBTools repo. github.com/HALTEC/VBA-commons-lib I put all of it under the Apache license.
Then why Err.Raise at all? What kind of errors are you trying to overcome?
To be more precise, what I mean is most errors you will encounter are predictable. If you think ahead when coding you can catch the majority of errors and try to correct them. Depending on if you are coding for other programmers or non-programmers they may or may not be able to help fix the problem. I tend to think ahead, and if I cant let it error out and put something in a log file that I can use to debug it.
I'm updating legacy code that used End in VBA to execution. Rather than having that occur I want some way to indicate why it's being stopped and to gracefully exit.
My personal approach is to use an alert to tell the user the same info that Err.Raise does, but I can include a custom message like "Exiting the routine." or "Come see me if you have this error." Something more useful. I also use a separate routine for handling errors that I am going to end on.
This allows me to change my Error handling approach in one routine, and not in all the subroutines. I just use Boolean function calls. On error, return true, if true goto errorhandler.
@IvenBach set up an error handler at every single one of your entry points (macros, workbook/worksheet event handlers, etc.), and msgbox the error (or log it.. whatever)
what you want is for any fatal error anywhere in the call stack to bubble right up to that entry point error handler, so in the procedures called from there, you'll have error handling that handles what can be recovered (e.g. return false), and re-raises (Err.Raise Err.Number) anything that can't, possibly altering the source and/or description so that you get something meaningful to work with. What's recoverable and what isn't is entirely up to your logic.
The web-dev covered stuff like C# (I pretty much aced that bit), SQL (I did pretty good on this), AJAX (I did pretty good on that, thanks to the senior project I did), and web dev stuff (I did terrible on that, probably because I skipped most of those questions because I had no idea what they did).
@IvenBach I'm not allowed to do manual labor on this job.
Could you imagine being the person reading those tests? There would have to be hundreds if not thousands of people who would still use Select and Activate.
Even worse if the hiring company didnt see that as an issue though.
Yeah, but I think it is part of the fact that VBA is a more user-friendly language to learn. It helps write the code for you. Some people dont know how to get past that.
Why would you? Unless you need something selected of course, but jeeze. If you deliberately do it in C# I would love to know the path you took where you didnt realize the error in your ways lol
> I have a Word 2016 project that compiles without error but gives multiple Resolver Errors. The resolver error message isn't too helpful as it just identifies the module. How do I go about tracking the problems.
> Go to Rubberduck settings, enable ERROR-level logging. Close everything, open up the failing project and reproduce the errors; the log file will contain detailed stack trace information we can use to diagnose the problem.
> Go to Rubberduck settings, enable ERROR-level logging. Close everything, open up the failing project and reproduce the errors; the log file will contain detailed stack trace information we can use to diagnose the problem.
I'm also quite flabbergasted by Dim k&, given you're not using type hints anywhere. Why not give it an explicit, named type like everything else? — Mat's Mug21 secs ago
@Mat'sMug ADODB question - there's no way to see the final post-parameter query that SQL Server is executing, right? I assume no because it's all server-side, but I'm having trouble with my parameterized query. I think it's returning no results because it's using the literal question mark rather than my parameter.
(Executing an unparameterized version in SQL Server returns results)
Good guess, but no, it seems to be going through cleanly: select distinct claimid as RejectedClm into #DRS1 from (Schema).(Table) (nolock) where claimid in (?);
Function PrepareQueryCommandAndParameters(ByRef cnn As ADODB.Connection, ByVal strParameterizedQuery As String, ByVal strClaimsToQueryThisRunVal As String) As ADODB.Command
Dim cmdtemp As ADODB.Command
Set cmdtemp = New ADODB.Command
With cmdtemp
.ActiveConnection = cnn
.CommandTimeout = 0
.CommandText = strParameterizedQuery
Dim parClaimsToQueryThisRun As ADODB.Parameter
Set parClaimsToQueryThisRun = .CreateParameter("ParClaimsToQueryThisRun", adBSTR, adParamInput)
Set cmd = PrepareQueryCommandAndParameters(cnn, strParameterizedQuery, strClaimsToQueryThisRun)
Set rst = New ADODB.Recordset
rst.Open cmd
```` 2017-04-26 21:14:13.1116;INFO-2.0.13.32288;Rubberduck.App;Rubberduck version 2.0.13.32288 loading: Operating System: Microsoft Windows NT 10.0.15063.0 x64 Host Product: Microsoft Office 2016 x64 Host Version: 16.0.7870.2031 Host Executable: WINWORD.EXE; 2017-04-26 21:14:58.8156;ERROR-2.0.13.32288;Rubberduck.Parsing.VBA.ParseCoordinator;Exception thrown resolving 'Project.clsArcinovaCTDTitle' (thread 7).;System.NullReferenceException: Object reference not set to an ins
@Mat'sMug Thanks for pointing me in the right direction. You saved me a ton of time of stumbling around before finally learning what was wrong. I still don't completely understand, but I do understand that In clauses are expecting a list of parameters rather than a single parameter, and I have seen some alternative ways of tackling it, including your own: codereview.stackexchange.com/questions/46312/…
All the questions/answers I have seen so far are old and do not provide a definitive answer.
Also what can I use locally and what can I use online?
VBA Rubberducking
VBA Rubberducking