Forum Discussion
Access web apps will be read only on April 1st, please plan accordingly
I have written a series of blog posts on rescuing your data from its Soon-To-Be-Late AWA. If you haven't yet figured out how you're going to do that with your data, right now would be a very good time to get that taken care of.
Perhaps we should pursue your claims in a different venue or at a different time?
Now I am wondering if, perhaps instead of Access Web Apps, what you are offering to convert would actually be the older, Access Web Database format, which was based on the older, SharePoint lists, running from a SharePoint site?
That, of course, is not particularly unusual. There is a native functionality within that format to convert them to a desktop accdb.
The claim that you are able to convert Access Web Apps, including forms, and including reports--which don't even exist in Access Web Apps--is what piqued my curiosity. Indeed it would be quite an accomplishment to do the latter.
However, pending clarification of what your tool does, I guess it's best to let it go for now.
Thanks anyway.
George Hepworth
Co-Author Professional Access 2013 Programming (2013 Access Web Apps)
Co-Author Microsoft Access In a SharePoint World (2010 Access Web Databases)
Hi George,
Yes, I was referring to conversion of Access Web Databases (2010 format .accdb files), not 2013 format Access Web Apps. I was just editing my previous posts to clarify that before responding here. Thanks for pointing that out.
Access doesn't natively support fully automated conversion of all objects from Access Web to Desktop databases, which is where this automated feature comes it. For Access Web Apps, I had touched on PowerApps as one alternative since there is still work required to convert to Access Databases.
The conversion feature is one of a few hundred features and functions provided by PowerAccess and PowerGit, but I thought relevant to point out, considering the deprecation of both Access Web Databases and Access Web Apps.
- So, thanks for clarifying that your tool is not intended to address the problem of expiring Access Web Apps, but for the previous version of Access Web databases. It would have been interesting, indeed, to do something with AWAs, but as we both know, that's not going to happen. The only thing possible there is to rescue the data itself; none of the interface objects.
This particular article in which we are participating, of course, refers to the end of support for Access Web Apps. Coincidentally, that does mean the old Access 2010 version Web Databases will also stop working at the same time, but it's hard to imagine there were still very many of them in use at this point anyway, fortunately.
In any event, thanks again for clarifying what your tool can, and can't, do.
Best of luck. Out-of-box Access fails to import most objects from Access Web Databases to Access Desktop Databases.
You can compare the results of manual, partial importing of each object vs. use of PowerAccess | PowerGit for complete, automate conversion in the attached zip.
The attached zip file (PowerAccess Automated Web to Desktop Database Conversion Demo Results.zip) includes:
- Web Database .accdb file
- Partially Import Result (using tools built-in to Access) .accdb file
- Complete Automated Conversion result (using PowerAccess | PowerGit) .accdb file
- PowerAccess Conversion Results Readme.txt" readme file
As detailed in the Readme file, manual conversion using built-in Access import tools only results in the following objects being imported, with all objects for Web Database use, except for Tables, failing to import:
Results of (Partial) Manual Import of Objects from Access Web Database to Access Desktop Database:
- 0 / 18 Queries
- 0 / 53 Web Forms
- 4 / 4 Desktop Forms
- 14 / 14 Tables
- 0 / 6 Web Reports
- 6 / 6 Desktop Reports
- 1 / 1 Desktop Macros
- 0 / 6 Web Macros
