tag:blogger.com,1999:blog-8134759511126815909.post4340119703950290594..comments2023-08-20T04:10:01.095-04:00Comments on <a href="http://rogersaccessblog.blogspot.com/">Roger's Access Blog</a>: Access Web Databases: 2010 vs. 2013Roger Carlsonhttp://www.blogger.com/profile/12265719129831415014noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-8134759511126815909.post-89005419924849396052015-10-02T16:54:55.492-04:002015-10-02T16:54:55.492-04:00Ken,
I should clarify my conclusion. I meant that ...Ken,<br />I should clarify my conclusion. I meant that IF one wanted to start a new Access web project, 2013 should be your choice as opposed to 2010. <br /><br />Your concerns about Access as a web development environment certainly have validity and should be considered before beginning a new project. <br /><br />Thanks for your commentsRoger Carlsonhttps://www.blogger.com/profile/12265719129831415014noreply@blogger.comtag:blogger.com,1999:blog-8134759511126815909.post-50770443055115039672015-10-02T16:01:18.406-04:002015-10-02T16:01:18.406-04:00Hi. Sorry for the late post.
Your article clearly...Hi. Sorry for the late post.<br /><br />Your article clearly explains some of the differences between 2010 web databases and 2013 web apps. But your conclusion is wrong:<br /><br />No one in their right mind should do serious web development in Access.<br /><br />Microsoft has had a recent history of instability in their peripheral development platforms: dumping 2010 'web databases', abandoning Silverlight, and their de-emphasis/possible abandonment of LightSwitch. Developers investing in these technologies lost out.<br /><br />But, looking at the scant information available, it appears Access 2016 will continue with the 2013 'web app' platform, and provides a small list of incremental improvements, to be rolled out in conjunction with Sharepoint 2016.<br /><br />Still, in light of Microsoft's previous actions, it is fair to ask these questions: Is there a reasonable expectation that the 2013 'web app' platform will be around 5 years from now? It it worth the risk to develop something significant in this platform?<br /><br />Is there any indication that there will even be a version of Access after Office 2016?<br /><br />I maintain that Access, whatever version, is hopelessly outclassed as a web development platform. It's obvious lack of traction in the web development arena attests to this. <br /><br />Successful open source development platforms have proven to be far more stable over the long run than Silverlight, Lightswitch and 2010 web databases have been. .NET languages now enjoy strong cross-platform support, and are likely to have long lifespans.<br /><br />I strongly feel your readers will be far better served if they choose to develop their web apps using Visual Studio MVC or MVVC, or a major open-source platform. The initial learning curve is steeper, but that is outweighed by the long-term benefits, and the much higher probability that these platforms will be around in 5 years.<br /><br />-KenUnknownhttps://www.blogger.com/profile/14989315766774647485noreply@blogger.comtag:blogger.com,1999:blog-8134759511126815909.post-29060714473462957372015-02-10T19:40:04.976-05:002015-02-10T19:40:04.976-05:00Hi Grant. Thanks for your comment.
Unfortunate...Hi Grant. Thanks for your comment. <br /><br />Unfortunately, the answer is no, you can not extend your web app through SQL Server stored procedures. <br /><br />Macros you create in the Macro Designer are, in fact, converted to stored procedures behind the scenes, but the only way to modify them is through the Access macro designer. You also cannot create your own, custom stored procedures and have them available to the web app.<br /><br />I wish I had better news for you. <br /><br />I can't really talk much about what I know of Access' future, but, I can say the next version should not repeat the incompatibility issues as between 2010 and 2013. Roger Carlsonhttps://www.blogger.com/profile/12265719129831415014noreply@blogger.comtag:blogger.com,1999:blog-8134759511126815909.post-42357804494482501522015-02-10T17:12:47.602-05:002015-02-10T17:12:47.602-05:00I guess my most pressing question about this would...I guess my most pressing question about this would be, since the data lives in SQL Server now instead of SharePoint lists, does that open up the development of 2013 web apps to use some of the more advanced features of SQL?<br /><br />One of the biggest difficulties I've had in developing 2010 web databases was the pure lack of features. Some much-needed nesting (like using data macros to populate another table from data in an existing table, using a "CreateRecord" inside a "ForEachRecord") was impossible by design.<br /><br />You could build functional simplistic systems using it, but very quickly you would learn doing anything more with your data is nearly impossible without a dedicated desktop app. <br /><br />Part of me wishes there was more warning to users before encouraging them to jump into a web app/database development project without realizing they've locked themselves into a corner, the only way out being back to the beginning to start all over again.Anonymoushttps://www.blogger.com/profile/11306013587137489993noreply@blogger.comtag:blogger.com,1999:blog-8134759511126815909.post-87697541049798041532014-05-05T20:07:32.869-04:002014-05-05T20:07:32.869-04:00Roger, this is great. You have a gift for researc...Roger, this is great. You have a gift for researching, sifting to essentials, and writing.<br /><br />I was doing dev with 2013 using Win 8 on my laptop ... remember the one you helped me write the letter for a couple years ago? Well, anyway, it bit the dust and I'll never trust Asus (or their lousy service) again. So now I have Win8 and Office 2013 on another boot drive ... but I rarely switch over. Hoping for bucks I can divert to another laptop this summer -- then it will be easier to develop in the newer environments. But I digress ...<br /><br />This article makes things clear for anyone wondering about Access web apps and web applications in the mass of confusion. I have saved this link to pass on. Thanks again, Roger.<br /><br />Warm Regards,<br />Crystal<br /><br />Data Dictionary, Display Control<br />by Crystal on RogersAccessLibrary<br />http://www.rogersaccesslibrary.com/forum/data-dictionary-display-control_topic610.html<br /><br /> *<br /> (: have an awesome day :)<br /> *Crystalhttp://www.accessmvp.com/strive4peacenoreply@blogger.comtag:blogger.com,1999:blog-8134759511126815909.post-12876681503986571362014-03-21T14:42:36.323-04:002014-03-21T14:42:36.323-04:00I have been developing in Access since version 2.0...I have been developing in Access since version 2.0. And I must say I feel lost with the Access Web Apps. This is clarifying some misconceptions I had. Thanks. Please keep posting your journey Andres Dominiccihttps://www.blogger.com/profile/05681800745238115326noreply@blogger.comtag:blogger.com,1999:blog-8134759511126815909.post-2803356476897385902014-01-14T18:39:31.627-05:002014-01-14T18:39:31.627-05:00Excellent article. Your explanation of a difficult...Excellent article. Your explanation of a difficult subject is clear and to the point and your advice is spot on. It helps clear up a lot of the confusion about the new Access 2013 Web Apps and the 2010 Web Databases. I look forward to reading more about this subject. Patrick Woodhttp://gainingaccess.netnoreply@blogger.com