A quick word of caution and tip of the day regarding doing development using the Microsoft Access Modern Web Browser control.
With the extensive development I have done with the Modern Web Browser control, I have noticed some inconsistencies in it reflecting updates I have made to code during development.
Yesterday, I presented an approach to manage to display an image in the old Web Browser control so it was resized to fit a given box while retaining its aspect ratio, you can read the details by reviewing
I figured I quickly demonstrate the required code to do the same in the new Modern Web Browser control since the is a better simpler approach that we can employ which reduces the HTML/CSS required.
So I came across a recent question on UtterAccess
and figured I’d share something I had done many years ago.
So, I went digging, and well, couldn’t locate the project. 🙁
So, I figured I had done it once, I could simply do it again and I did.
The entire thing here is resizing the image isn’t complicated, but preserving the aspect ration is a little tricky. Normally, we would simply apply the desired height/width attributes to the image itself, but that will distort the image. I also didn’t want to get into downloading the images locally to be able to read their size properties (height/width) to then be able to calculate the proportional dimensions to respect the desired size, just not efficient and a waste of I/O operations… So we need another approach.
I should also quickly mention that the following is a solution for the old Web Browser control and there is simpler code to do the same thing in the Modern Web Browser control (maybe another article in the coming days/weeks).
What is Compact and Repair (C&R)?
What does it do exactly?
Why do most experience developers recommend it so much?
Well, these are some of the questions that I am going to try to answer in this article. So let’s take a closer look at Microsoft Access’ Compact and Repair command.
I recently released a YouTube video regarding the Compact and Repair command.
My objective with that video was to only summarily touch upon the command, how to run it and explain the 2 main benefits. I was aiming for a video for new users, and introduction to the subject.
I received a negative comment stating that I didn’t explain the causes of bloating …, I didn’t delve into the details of the issue enough. Thus, I thought that today I’d start trying to cover some of the more known root causes of database boating and will most probably create a follow-up in the future to discuss this further.
So in a previous post:
I demonstrated how one could easily integrate the means to crop images. This was fine and works very well.
That said, I wanted to push things further. I know that quite often, I need to do a little more than just crop an image. I don’t need a full blown editor like Photoshop, GIMP, Paint.net, … but I do need the ability to resize, crop, insert some text and a few other simple things (from time to time).
Wouldn’t it be nice if we could do all of this in Access directly and no longer need 3rd party applications, or ActiveX controls? Wouldn’t it be nice if we could have a seamlessly integrated full fledged image editor in a Microsoft Access form!
I’ve spent a lot of time messing around with the Modern Web Browser control and specifically trying to dynamically render content. My most recent adventure relating to this allowed me to finally finish a project I had tried developing years earlier, but was limited by the ‘original’ Web Browser control’s functionality (or lack thereof):
Once again, Microsoft has no documentation whatsoever on this aspect of programming the Modern Web Browser control! So this was a massive trial and error type of development and being too stubborn to give up, I eventually found a way. What is nice here is the fact that the final solution is very straightforward (although getting there was not).
I lied. I’ll be the first to admit it. In my post
I said I was done with the Modern Web Browser control. Apparently not!
So I was doing some house cleaning and came across a project I had developed several years back, but wouldn’t work because the old web browser control didn’t support HTML canvas elements and I had shelved it.
Oh what a fun couple of hours I’ve had trying to revive a project I had started using the old Web Browser control and was trying to convert to use the Modern Web Browser control.
I did find, yet another, limitation when trying to dynamically populate the Modern Web Browser control!
It would seem that you cannot use absolute paths.
Just curious if anyone else testing the Modern Web Browser control has been experiencing rendering/display issues similar to: