| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 141604 | 2016-01-19 21:53:00 | Access 2010 and Windows10 | Tony (4941) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1414716 | 2016-01-19 21:53:00 | I created and continue to maintain an admin system for an organisation I'm involved in. It currently uses Access 2010 and runs on Windows 7. They have been told by their IT supplier "The application won't run on Windows 10", for unspecified reasons. I've been told various possibilities but I'm hoping someone here can clarify for me. The system dates from about 2002 and uses the ".mdb" database format and DAO. It probably should have been changed to .accdb and ADO but it has been a case of "if it ain't broke, don't fix it." So, questions: Is mdb/DAO unsupported on Windows 10? Unfortunately I'm not in a position to install Access 2010 on Win10 so can't prove/disprove it. Is mdb/DAO also unsupported in later versions of Access? I may have to change to Access 2016 and I need to know if this is an issue. If I do change and also change the application to .accdb/ADO using Access 2016, will that still run on a system (Win7 or Win10) that still runs Access 2010? If it won't run, can I use the Access 2016 runtime to package the app to run on Win7/Win10? Is there any other reason the application might not work on Win10? Any insights welcome. |
Tony (4941) | ||
| 1414717 | 2016-01-19 23:02:00 | They have been told by their IT supplier "The application won't run on Windows 10", for unspecified reasons.. Ive had instances where Ive been told an app wont run on the newest version of Win, yet it did, without issue . That sometimes means they hasnt been tested it on that OS, so its easier for them to say its not compatible. That way they dont have to try & support it on that OS. Not much help, I know . |
1101 (13337) | ||
| 1414718 | 2016-01-20 02:00:00 | Microsoft had some pages addressing this. Basically much of Office Apps are so far working ok on W10, with the exception of Outlook. MS however won't stick their neck out and guarantee functionality, and acknowledge there may be instances where lesser used routines fail. Personally, I'm of the belief that the free W10 is just a trap, where they'll introduce changes that essentially force folk to upgrade their Office suites if they want to eliminate the 'issues' that follow these OS updates. MS will claim innocence, stating that W10 is fine, and that it's the outdated Office apps that are the problem. They want your money. Giving stuff away isn't going to be how they continue to operate. |
Paul.Cov (425) | ||
| 1414719 | 2016-01-23 04:09:00 | I have Access 2002 running under Win 10, no problems. I created and continue to maintain an admin system for an organisation I'm involved in. It currently uses Access 2010 and runs on Windows 7. They have been told by their IT supplier "The application won't run on Windows 10", for unspecified reasons. I've been told various possibilities but I'm hoping someone here can clarify for me. The system dates from about 2002 and uses the ".mdb" database format and DAO. It probably should have been changed to .accdb and ADO but it has been a case of "if it ain't broke, don't fix it." So, questions: Is mdb/DAO unsupported on Windows 10? Unfortunately I'm not in a position to install Access 2010 on Win10 so can't prove/disprove it. Is mdb/DAO also unsupported in later versions of Access? I may have to change to Access 2016 and I need to know if this is an issue. If I do change and also change the application to .accdb/ADO using Access 2016, will that still run on a system (Win7 or Win10) that still runs Access 2010? If it won't run, can I use the Access 2016 runtime to package the app to run on Win7/Win10? Is there any other reason the application might not work on Win10? Any insights welcome. |
Jayess64 (8703) | ||
| 1414720 | 2016-01-23 04:14:00 | I have Access 2002 running under Win 10, no problems.Crikey, Access 2002! That's pretty ancient. I've come to the conclusion that there is most unlikely to be a problem. What I'm going to suggest to them is that they do the change to Win10, try the system, and if there are problems, roll back to Win7 then decide what to do next. | Tony (4941) | ||
| 1414721 | 2016-01-23 05:17:00 | If for some stupid reason it doesn't want to run on W10, then right click on the application (Access) and tell it to run in compatibility mode. Had to do that with several other programs I use, one was designed for XP wouldn't run on W8 onwards. Works fine "Now" in W10 in compatibility mode. |
wainuitech (129) | ||
| 1414722 | 2016-01-23 07:43:00 | If for some stupid reason it doesn't want to run on W10, then right click on the application (Access) and tell it to run in compatibility mode. Had to do that with several other programs I use, one was designed for XP wouldn't run on W8 onwards. Works fine "Now" in W10 in compatibility mode. I don't expect there to be a problem but that is certainly an an option if there is. Thanks. |
Tony (4941) | ||
| 1414723 | 2016-01-31 22:16:00 | I don't expect there to be a problem but that is certainly an an option if there is. Thanks. just because something works doesn't mean that the developer chooses to "support" it that sounds like the issue here. regardless if something actually works or not, if the person that supports the software chooses to not support it, its not supported. the modern way that Windows deals with servicing/upgrade/updates - Windows as a Service will challenge ISVs like the one you've described to rethink their business models. It will become unacceptable to not "support" customers who choose to move their version of Windows to something that is fully supported (ie Windows 7 is already in Extended support) |
nmercer (3899) | ||
| 1414724 | 2016-01-31 22:43:00 | just because something works doesn't mean that the developer chooses to "support" itThe developer in this case is me, and I'm quite happy to support what I developed. The issue arose because the person who supplies hardware/software to the club said that the Access 2010-developed app wouldn't run on Win10. I've come to the conclusion he is either ignorant or misinformed on the topic or misunderstands the way the app is implemented. As I said a couple of posts ago What I'm going to suggest to them is that they do the change to Win10, try the app, and if there are problems, roll back to Win7 then we decide what to do next. |
Tony (4941) | ||
| 1 | |||||