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.
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).
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:
First brought to my attention by a comment from Darvin Martin, there appears to be another major limitation with the Modern Web Browser control.
It would seem that you cannot mix content sources. Let me explain …
Even though the Microsoft Access Modern Web Browser control made its appearance back in May, it has taken Microsoft 3 months to make any form of an official announcement, show any form of pride in their own work!
As they say:
So here’s their official blog/release notification:
Recently, on my YouTube channel, @user-do9yi7gs4u asked when the (Microsoft Access) Modern Web Browser control would be available for Enterprise users.
So, several days ago I put the question to the Access Dev Team. I just heard back and here is the planned release cycle breakdown:
For any of you trying to get a grasp of the new Modern Web Browser control, beyond my set of articles on the subject found here, I have also started to release a YouTube series of videos. Below is a direct link to the Modern Web Browser playlist:
Over the years, I have seen countless posts regarding images in reports rendering very pixelate images even though the image itself was of decent quality & displayed and printed fine in other applications.
Access seems to always render default bmp, wmf or ico formats, but outside of those things can get dicey at times.
Some have said this issue became more of an issue when Office 2007 came out. I can neither confirm nor deny this claim.
Now there are plenty of suggestions out there, and there were some fixes put out over the years (images not rendering at all, …), but today I thought I’d offer up another potential workaround.
