Link to home
Start Free TrialLog in
Avatar of DataQuest
DataQuestFlag for United States of America

asked on

Lack of Database Documenter for Access 2013 Apps

When editing an Access 2013 App, the ribbon does not include the Database Documenter under the Database Tools tab. I understand that the reasoning behind this situation is that the data tables are being stored in SQL tables on SharePoint, but that doesn't make up for the frustration of not being able to generate the type of documentation which is possible for an Access 2013 Desktop program. Related to this is the lack of being able to graphically view the relationships between tables; again, I already understand that the "relationships" are built in a lookup field that gets values from a related field in another table. But knowing that doesn't solve the lack of being able to view and document what's going on... Any suggestions for documenting an existing Access 2013 App which is running on SharePoint?
ASKER CERTIFIED SOLUTION
Avatar of Jacques Bourgeois (James Burger)
Jacques Bourgeois (James Burger)
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Avatar of Scott McDaniel (EE MVE )
Scott McDaniel (EE MVE )
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of DataQuest

ASKER

James,
That link was helpful for pointing me in a direction where I could at least gain some insights. The Access 2013 Apps in Question are being run on SharePoint with an E3 subscription. Do you know whether Microsoft makes it possible to look at those SQL structures with the tool you were referring to?
Thank you.
Scott,
It's an Access 2013 App, not a Desktop "app"; my understanding is that the iteration which ran under Access 2010 included the word "Web."
That FMS website was very interesting, I am going to keep that one in mind for future needs.
Thank you.
It's an Access 2013 App, not a Desktop "app"; my understanding is that the iteration which ran under Access 2010 included the word "Web."
2013 can create both Web Apps and Desktop Apps - but it sounds like this was created in 2010 as a Sharepoint-hosted web database.

If so, then the documenter should be able to review the database structure to some degree.

If it's a Web App (i.e. you're running Office365 and you have to "launch" the app from a URL) then I'm not sure what could be done with that ...
Okay, it's a Web App. Purchased another book (published by Microsoft) and the distinction was much more clear.
Some points were awarded for suggesting the FMS site as a source of tools/information.
Thank you to you both!
I'm curious - which book did you purchase?
The first book, which doesn't (to me) seem to emphasize "Web" App was: Professional Access 2013 Programming, by Teresa Henning, et al.
The second book, which does emphasize (SharePoint hosted) the term Access Web App was: Microsoft Access 2013 Inside OUT, by Jeff Conrad.
Both are very well written, and I am enjoying going through each of them.