Search results

As I said in the OP the problem didn't manifest itself until a recent Office update. Working on testing that theory here in a bit that a rollback fixes it. The form/code behind hasn't changed there in some time.

Yes if rolling back doesn't fix it I am in the process of changing to me.dirty = false instead.

Yeah I get why it tells me that, but in this case the user hasn't edited anything. It seems like some sort of regression from an earlier version of Access(Office) as it's a 'new' problem.

I've been using the Field Effect Access SQL Editor for a while. I like it quite a bit and the dev is responsive if you have questions or bugs.

Since updating to LTSC 16.0.14332.20416, I've got one user (others haven't seen the upgrade yet) complaining when he hits this button in a form that's got a module behind it that runs DoCmd.RunCommand acCmdSaveRecord then fires a bunch of stuff off to a PDF printer a message box with the title...

I recall reading somewhere the rollback was due to the issues with Access (the DAO.Field3 thing, and the control borders). Not sure where, and of course I cannot find it now.

There were no changes listed in the aforementioned version that started this thread either.... hence why I thought I was "safe" from Access bugs on June 29. That said. 2206 15330.20196 broke the control borders in report, they then took that version off the CDN and my apps rolled back to 2205...

The re-release of v2206 (15330.20230) on July 6th, 2022 seems to have remedied this.

Can't say I've seen this one.

Mine didn't even ask, it just rolled itself back over the long weekend.

Sure. The rollback / feature gates are cool. But wrapping every new change in a some sort of conditional probably sucks unless there's some automation behind it. It also makes one wonder what exactly they were adding/removing/changing to break control borders in reports that also required...

Thanks Colin, Can confirm borders are back.

Looks like rs.Fields defaults to a DAO.Field3 type (which seems new) instead of the prior default. https://stackoverflow.com/questions/72831316/access-with-breaking-changes-on-version-2206-recordset2-fields-returns-dao-fiel

Yikes.

Indeed. I'm just glad it was confirmed quickly and hopefully an update pushed out relatively quickly too.

Gustav Brock? he's part of the mailing list I'm on so maybe he relayed it.

Nothing in the DB but "report1" with a bunch of controls with borders. Print preview or print to a printer and your borders vanish. As far as the Access MVP group, I'm not a part of any of those (but would love to be). This was another access development mailing list that I'm part of.

Hey GPG. The initial email was to a group of access developers containing basically what my post here contained. Then I reached out to someone on the MS Access team privately to ensure they saw the issue. We bounced a few emails back and forth and I sent them an example database to reproduce...

Colin, It was in an email discussion with someone on the Access team. There's no link to provide at this time.

Bug identified by Microsoft. A fix is coming "soon".