@Duga Unfortunately, this is very unintuitive and not well documented. The wiki reads, "When synchronizing attributes, this will add or update the module's VB_Description hidden attribute:" Granted, that does say "syncing", but that one word doesn't adequately describe the process of adding the annotation, parsing the project, looking at the inspections and applying the proper fix (is there a "fix all in project" quick fix for this one?).
> Okay thinking about this more, wouldn't there be at least a bit of generalization, like wouldn't you want the inspection to examine userforms too, for example?
Interesting, I'm not getting this when I connect to our Azure data warehouse. I don't recall having received this warning before, but I may have and may have suppressed the message on my other machine.
Since I'm not certain what these settings do, I'm pretty sure I don't use them, and that, therefore, it is reasonably safe to ignore this warning?
All good here. Y'all surviving without homicidal thoughts toward spouse or offspring?
;)
@FreeMan "I'm not getting..." Then why the heck you posting the message, you nimnod?
If only I could blame that on autocorrect or something... There's no autocorrect on the desktop machine, just incoherent typist
out of the blue, I'm getting this error from my Access application that was working just fine earlier last week, late the week before:
Source: Microsoft OLE DB Driver for SQL Server
Error Num: -2147467259
Description: SQL Server Network Interfaces: Error reading adalsql.dll path from registry. Verify that Active Directory Authentication Library for SQL Server is properly installed. For details, please refer to go.microsoft.com/fwlink/?LinkID=513072 [2].
some searching for the description string led me to this site where he indicated that the adalsql.dll file was present on the machine in question, but wasn't registered.
I've searched my machine, but I don't have that file at all.
Do I need to install the Active Directory Authentication Library for SQL Server locally on my desktop machine?
If so, why would I suddenly need it now when I didn't need it last week?
> Embedded Active Directory Authentication Library (ADAL). A separate installation of ADAL is no longer required to use certain authentication methods.
if you somehow downgraded to pre-18.3, then yeah, that'd be why.
hrm... I wonder if I did do an SSMS update last week. Yeah... I'm pretty sure I uninstalled and reinstalled everything SSMS, VS, and ADO/DAO related last week to get my laptop working.
@FreeMan my wife may want to go jack torrence on me, but on my end we're all good and things are fine. kids still have some day care so we get a little time to work, then unwind after
@this indicates that was released Oct '19. Since I just installed the "latest" download from MS last week, surely I'd have picked up v 18.3 or newer, right?
right?
@this you're fine. Just don't lick the toilet. That's gross.
"Intelligence is the ability to acquire and apply knowledge, and the lack of knowledge is ignorance. It is a sad world where the ignorant can stifle the intelligent, and morose when it is encouraged."
First post here. I sincerely hope that I am doing everything by the book. Also, I want to thank you in advance for any help and assistance that you may be able to provide me. I have been coding VBA for 2 weeks and I realise that my code may suck.
Problem:
What can I do to make my code faster? I ...
sorry... got distracted by putting my contacts in (nothing quite like the fun of poking yourself in the eye several times waiting for the lens to stick when the lens has already slipped down your finger and is no longer anywhere near where the poking part), then by the id10t telling other people to "note the self-reported data by adding an "*" to the otherwise numeric field"
ARGH!!! if the cell is supposed to contain digits, only put digits in it. If you need to make a comment about the number, then use Excel's bloody comment feature!
@this I don't think I need to go find the version info, I installed using msoledbsql_18.3.0.0_x64.msi. Unless, of course, they broke the installed and shipped an older driver with the new version in the filename...
doesn't trust MS to not screw it up, searches just to be safe...
ummmm.... the file versions reported are 18. 2 .0003.0. That's not right, is it?
Microsoft started development on the .NET Framework in the late 1990s originally under the name of Next Generation Windows Services (NGWS). By late 2001 the first beta versions of .NET 1.0 were released. The first version of .NET Framework was released on 13 February 2002, bringing managed code to Windows NT 4.0, 98, 2000, ME and XP.
Since the first version, Microsoft has released nine more upgrades for .NET Framework, seven of which have been released along with a new version of Visual Studio. Two of these upgrades, .NET Framework 2.0 and 4.0, have upgraded Common Language Runtime (CLR). N...
which is right about the time I was attempting to beat the laptop installs into submission. I spent Monday installing everything and Tuesday reinstalling.
bizarre - my windows can't find the OLEDB driver in programs & features in both places.
no, that's because it's "OLE DB"
hooray!
so apparently I've been running 18.2.1
I may have had it downgraded when SSMS updated and I didn't noticed yet
oh, this gets better and better:
let's play "guess the bitness" game!
Ok, updated and now it does show 18.3.0... in the details as expected
Well, that is very good that you shared your experience. Otherwise I'd never have realized that Microsoft sneakily downgraded my driver without ever telling me about it.
well, some sort of backup is always recommended. Even if it's just 2 cheapo 1TB external drives that you make backups to daily, then once a week swap for an offsite at the folks or a trusted friend.
well.. I've actually got two of these - one (currently?) broken. But I moved some stuff about in the house a while ago and never got around to setting them back up. I should probably address that...
Just waiting on those 20+TB HAMR/MAMR drives that have been "a couple of years away" for like 10 years now, then I'll be rocking some serious space.
Picked up a couple of 10TB WD Reds last Prime day, wish I bought more now. Maybe this year.
You may be interested in unRAID. Very low cost server software. Raid-like, but, as the name suggests, not RAID. I've been running a server for about a decade now, and it grows quite nicely as needed.
Fantastic support, loads of docker support (including a git server), and I think it'll even run on repurposed QNAP hardware.
Best part is that you can grow your storage by one drive at a time and they can be any size because it's not RAID
@FreeMan Hmm, interested. The broken one has a dud backplane, which are impossible to source. I'm gonna get an electronics chap to see if it can be repaired, but if not i'll just pick up a cheap HBA and hack the enclosure/mobo to run something other than Qnap OS.
Yeah, NAS software. It does require a parity drive for data protection (1 parity drive can survive a single drive failure, dual parity can survive 2 simultaneous drive failures)
The parity drive provides protection against data loss if a drive dies. However, I'd strongly recommend posting a question on the forums to get support on recovery.
It's shocking how many people seem to think formatting an apparently failed drive is the first step in data recovery
Frankly, I've had drives of many different brands. I'm a big proponent of "whatever's on sale when I desperately need one". I had one drive go bad back in the late 80s costing me data, but most of the data loss was my own fault, not the drive's fault. Bad attempts at recovering data were to blame.
with unRAID, there's a tremendous amount of disk health monitoring & notification (if you turn it on). The only data I've lost with it was, again, user error.
I deleted about 10TB of stuff by accidentally clicking the wrong thing then letting it run a while wondering why it took so long.
Fortunately, the critical stuff was backed up, so I restored. The rest involved re-ripping DVD/Bluray disks
so that just cost time.
I did lose quite a few ZIP disks to the dreaded click-of-death, though.
ahhh... the good ol' days when 100MB on a 3.5" disk media was massive storage
Oh I had one. Two, actually, if I remember correctly! One of the best things about the ZIP drives, is that they actually did the daisy chaining of the LPT port that USB promised and never delivered.
Because of the way my desk was setup, I had the 'puter on one side and the printer on the other. I used the ZIP drive in the middle with the longest LPT cables I could find/afford on either side. It was a powered LPT extension as well as storage!
I can't remember but there were many times where I had a zip disk and no drive; it wasn't practical to bring around the drive ( probably because it wasn't mine, or because it was shared among the family and thus had to stay with the computer ).
The other option was burning a CD. Everyone had burners, right?
@FreeMan My current plan involves RAID-6 (or equivalent), plus also backing up rips to externals, the latter being whatever size/quality I can acquire for cheaps (within reason). Once I get enough Reds, the seagates are gonna be relegated to offline backups.
ripping takes way too long for me to trust any raid entirely
I'd presume that our DBAs have set what they think are the best options. I just didn't recall seeing that warning. Prolly not a lot I can do 'bout it. Guaranteed there's not a lot I understand about it
of course, that interrupted me while I was trying to figure out how I'm missing 2 records for one client, and I've got 2 other clients, 1 is reporting 1 more record than it should and the other is reporting 1 less than it should.
A simple query of the DB is showing the right numbers, I'm just not picking them up in my reporting query.
AAAARRRGH!!! No wonder I was pulling the wrong numbers, the queries were looking at different date columns. :( Took a lot of looking to finally see that...