I know, this isn’t anything new, but I still view it as a bug. Why is it if I Cut a control on a form to go and paste it in the same form elsewhere, we loose any associated events? The code remains in the Form module (VBE), just the event property value of [Event Procedure] are lost.
After my recent article regarding the Modern Web Browser control always appearing when placed on a tab control:
I decided to do a little more testing, as this was one thing I had never explored before, well not with the Modern Web Browser control at least.
Sadly, things went downhill!
A small UX bug in MS365 in which on the Ribbon for Form Design the Tab Control icon is sideways???
Well, there’s yet another issue with the Modern Web Browser control!
This is one I didn’t find myself, but that one of my viewers brought to my attention via my YouTube channel.
If you’re not up on the news, Microsoft has decided to deprecate and remove VBScript!
A while back, I published a short video of issues I experienced with Microsoft 365 (MS365):
I thought things were resolved, but yesterday more licensing issues surfaced.
I used MS365 the day before, all was good, yet suddenly now it reports (Unlicensed Product)? Say What!
I’d get a pop-up to “Sign in to get started with Access” even though I was already signed in?
So, I’ve been working on putting together a few Slider control options and wanted to provide a Web based solution as Sliders have long existed in HTML and are far more customizable since everything can be configured via CSS!
It took but a quick Google search to find an IE compatible Slider that I wanted to incorporate into a ‘Legacy’ Web Browser control.
I quickly created a stand-alone HTML file, tested it in IE to ensure all was well and it worked perfectly!
I was ready to now bring it into my Access database! Setup the control source, test it out and what do I get?!
Well, 96% of people indicated that they want to learn more about creating Slider controls.
So, in this post, I start covering the subject by introducing the ‘simplest’ (maybe not quite, but what you would think would be the simplest) slider control built entirely using a couple label controls and a command button.
I will post a few more articles in the coming days that will cover other possibilities:
I’m always amazed at the level of pure stupidity that Microsoft exudes at times!
I know, we all have our moments in the sun, myself included, but Microsoft just seems to manage to outdo themselves.
I’m well aware that in an ideal world, Microsoft wants us all running MS365 and thus we would have all migrated all of our existing Web Browser controls to use the ‘new’ Modern Web Browser control, but that isn’t reality, not even close! The fact of the matter, the legacy Web Browser control is still fully supported and thus why fix something that isn’t broken. Beyond which, many people are simply not running MS365 so they don’t even have access to the Modern Web Browser control at all.
All of this to say, that many a database are still using the ‘Legacy’ Web Browser control, thus IE (Internet Explorer)!
In a push to refresh the Access interface I published a couple articles and videos showing how we could pull HTML menus into Access, add security, control what was accessible by whom, drive the content from tables, …
Along the same train of thought, I have been exploring trying to simplify data entry and one of those aspects brought me to Sliders!
Instead of needing to switch to the keyboard, simply dragging a slider can simplify data entry. It also gives a more modern look and feel to an application.
