Search results

This may or may not be what's at work but you do have a case of ambiguous naming that could lie at the root of your problem. The "Sex" case may be unique in your dB but you should verify other instances of the same difficulty don't exist. To the point, Access does best when objects have...

DLookup() is nifty as far as it goes but can be optimized in many ways. I developed a DLookup() clone (see below) to do just this, and designed it to be a drop-in for the OEM function. This won't address your network latency issues but may speed things a bit. I haven't tried it but I expect...

Re events, I haven't tried it yet but I expect one can sink events in a standard module via a module-level object variable declared WithEvents. What definitely can't be done is raise events to be sunk elsewhere. That requires a module instance being assigned to a remote WithEvents variable...

@MajP , you're quite helpful, and thoughtful, to raise these points. It turns out I'm deeply familiar with predeclaration, not to mention other dark arts of attribute manipulation, and have implemented it on a number of occasions. It's nifty as far as it goes but has its limitations. Most...

It's good to know that the compilation process provides a firewall of sorts in this regard. That probably rules out most of the risk scenarios I could envision and leaves me far more confident that a "Namespace" property or function won't court disaster. This said, I have discovered that...

The procedures in the same module need to pass a Form variable (not the form's name) when calling RepositionForm(), just as when calling it from a form's module. No telling what those procedures do, with what, or from where they are called but somehow, they need to gin up a pointer/object...

Pete, this was my initial take as well and thanks for confirming. As noted in my prior response, which was written before yours but delayed in posting, the project does in fact compile and, after a bit of churn on closing, things settle down. Actually, it is a property of a standard module. I...

Thanks, no, I didn't see it on the VBA list of reserved words, either, although it's definitely on the VB.NET list. There isn't an express naming conflict in the app. The property is the first use of "Namespace" in the app, ever. Also, the project does compile, after all, and this ordinarily...

"Namespace" is reserved in VB.NET but is not documented as such in VBA, as far as I can tell. VBA bucks a bit when I attempt a "Public Property Get Namespace()" but seems to take the bit after compiling, saving, and cycling the app a few times. Lest I court disaster and before I go too far...

Perhaps but if so, she ought to be able to respond substantively rather than ad hominem. It's an interesting presentation but I've also studied event progression with equal or greater rigor, so I do, too. Perhaps she might learn something if she paid attention, read closely, and weren't so...

No disagreement but that is beside the point, which is that it isn't clear from the OP that the parent record, or form, is in question. He said the "main form," not the "parent form," was on a tab page. A tab control's parent can't be on a tab page. Common usage of course is that "main form"...

This is a reasonable expectation, as is the case with forms, and the documentation suggests this, as you say. Nevertheless, I have found it not to be case on several occasions. In the universe of controls. My specific findings are that Activate and Deactivate do not occur for subforms...

I departed A2007 at long last and now, on A2019, find that my apps' record selector backgrounds, scroll bar backgrounds, and scroll bar thumbs all are solid black. I've been rooting around fiddling with Windows, Office, and document themes and sundry registry settings, with no effect and Google...

Controls' Before and After Update events often do not occur, the documentation notwithstanding. Similarly, Form.Current and Form.Activate do not occur for subforms or pop-ups. The language describing controls' Change and Dirty events is identical but Dirty occurs only with the first change and...

Events occur when they do but sometimes not when documented. When conditioning code on them alone, the best one can do is to better understand their triggers and how to avoid them or make them happen, or to find another event, which often will be for another object. Updates can be triggered...

For <$1.00. LOL.

I did, of course. Amazon's, and Best Buy's, fine print are as described. Good to know Access is included notwithstanding the fine print but I'm reticent to drop $100 or more on a nonrefundable purchase on the expectation that undocumented features are included. To the point, though, I'm still...

That's curious, because on Amazon just now, in the U.S., at least, it isn't included in the Home, Home & Business, or Family 365 (subscription) versions. My recollection is that it hasn't been, for years, at least according to the listings. In each case, they're limited to Word, Excel...

No Access in the "Home" version, IIRC. I've done "bitness" Windows VMs before using VMware (on Linux but it shouldn't matter) with zero cost other than time and storage space. Quite helpful for running simulations back in the day when 64-bit MSO was considered experimental.

Understood but that's why I suggested a dm. Spill. ;-)