I came across a thread on UtterAccess:
and it brought back some memories of work I did for a client where I had to deal with this issue.
The issue is quite simple, exports, with the exception of PDFs, do not properly export all formatting.
Let me illustrate the problem, or at least one example of them.
Here’s another Microsoft Access bug that’s been around for a while.
This is another hit or miss issues, in that it doesn’t always occur, but it does happen enough that there a good chance you’ve seen before.
Here’s an issue that has been nagging me for years, the Midi Client close buttons not responding!
Here’s a screen recording illustrating the issue.
Today, I was preparing a demo db for a video I am hoping to make in the coming week and came across an odd issue with the Modern Web Browser.
Now, for full disclaimer, I haven’t done a deep dive into the matter. I simply identified the issue and implemented a workaround. So I don’t know if this is an issue with all cases, or just this particular site (I doubt it though).
I was trying to extract data from a site, so I created a variable representing all the matching span so I could then work with each one individually to perform other operations.
Just a short commentary about the inconsistent behavior, unreliability of the Microsoft Access Modern Browser control.
Just one more bug to add to the list, but I’ve been noticing rendering issues with the Microsoft Access Navigation Pane with lines & background color going beyond the boundaries of the Navigation Pane itself.
As shown in the following image, Access is drawing the Navigation Pane elements outside the Navigation Pane itself.
Recently I’ve been playing around a lot with Class Modules and Form/Report SubClassing:
and I recently stumbled upon an oddity, a bug relating to an Option Group’s border width property.
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.
For those of you that have tried to dynamically generate content for the Modern Web Browser control a warning that sadly this new control is simply unreliable and far inferior to its predecessor!
Have you ever needed to work with Conditional Formatting via VBA and tried to iterate through the FormatConditions collection?! Did you get incomplete results? Well, there is apparently a serious bug depending on the approach taken.
That being said, Microsoft did not push a fix for this bug to earlier versions. Thus, the workaround solution still remains the sole universal solution that will work properly on all versions of Access and as such, is the approach I recommend developers use.
The easiest approach to iterating over the collection is to do something like the following which is to iterate over the FormatConditions object:
Dim oFC As FormatCondition
Dim i As Long
For Each oFC In Me.FirstName.FormatConditions
i = i + 1
Debug.Print i, oFC.Expression1
Next oFC
Yet, this will fail to list more than 3 Format Conditions! Yep, you read that right. It will not necessarily list all the conditions. Making it worse, is I found no mention of this in the documentation (see below – maybe I missed it?!).