Feb 04 2022 05:24 AM
My program embedded in access does not work after upgrade to M-11 and program now in cloud.
Should I revert to M-10?
Feb 04 2022 08:01 AM
Please clarify what you mean by "m-11" and "m-10". Are you referring to Windows 10 and Windows 11?
Feb 07 2022 06:29 AM
Feb 07 2022 06:39 AM
Feb 07 2022 12:19 PM
@asmithj1 Thanks for clarifying.
You have an existing application created with MS Access. Under Windows 10 it worked correctly.
You upgraded to Windows 11 and now this same relational database application no longer "works correctly".
Unfortunately, we need much more detail to suggest any possibilities. Let's start with error messages. Do you now get any error messages when you try to use the relational database application? If so, what are the error numbers and error descriptions?
If there are no error messages, what DOES happen? What SHOULD happen? What is the difference between what you expect to happen and what does happen?
The more detail you provide, the more likely it will be that someone can gather enough information to suggest possible solutions.
Feb 07 2022 01:31 PM
Feb 07 2022 04:07 PM
I suspect that we may have a bit of a language problem here. Your program is not 'embedded' in Access in the normal meaning of embedded. Rather someone created the relational database application using the MS Access application to do so. Embedded means something quite different in English.
Also, m-11 is simply NOT a designation one encounters in computing. I believe we already decided that you actually mean Windows 10 and Windows 11, the operating system on the computer which is required to run the Access program. So, please understand if I use the proper term, Windows 11, here.
Now you indicate that this problem actually started at the same time many, many other users began to report a problem that was caused by an update to Windows 11 itself, not by the upgrade from Windows 10 to Windows 11. And that makes sense given what we know in general.
Here are two articles describing the problem and the workaround to recover from it.
Implement the workaround as described in the two discussions and please let us know if the problem is resolved.
Feb 12 2022 01:57 PM