DataBase - Export a List of Reports in Access

Asked By Connie
18-Mar-10 02:25 PM
I have an Access application which contains many reports(100+).  I am
trying to get a list of the reports without having to manually look in
the application to make the list.  Is there a way to export a list of
the reports with, perhaps, the fields utilized by the reports?
MSysObjects.ParentId
(1)
Access 2003
(1)
Excel
(1)
Documenter
(1)
Tremors
(1)
  Steve Schapel replied to Connie
18-Mar-10 04:40 PM
Connie,

Have you tried the Documenter?  In Access 2003 it is located via
Tools=>Analyze=>Documenter.

--
Steve Schapel, Microsoft Access MVP
  Gina Whipp replied to Connie
18-Mar-10 05:03 PM
Connie,

Open a query to SQL view and copy/paste the below in the window...

SELECT MSysObjects.Name
FROM MSysObjects
WHERE (((MSysObjects.ParentId)=-2147483645));

Do NOT change any of the names of *anything* as this is an internal table
used by Access.  Close and save and export it to Excel.

--
Gina Whipp
2010 Microsoft MVP (Access)

II

http://www.regina-whipp.com/index_files/TipList.htm

I have an Access application which contains many reports(100+).  I am
trying to get a list of the reports without having to manually look in
the application to make the list.  Is there a way to export a list of
the reports with, perhaps, the fields utilized by the reports?
Create New Account
help
DataBase Roger Jennings on Access / Sharepoint http: / / www.quepublishing.com / articles / article.aspx?p = 1606238 I was very dismayed reading is it makes it pretty clear that in-house hosting of your Sharepoint server with Access Services to support browser-based Access apps is something only large companies will be able to afford, because the pricing and licensing for the Enterprise version is very, very steep. The alternative is hosted Sharepoint / Access Services, and the costs do not seem terribly high. It seems to me that the pricing is upside-down. Big enterprises do not want to deploy Access apps in the browser - - they will build their own .NET apps, browser-based or not 2010, it could vastly increase those costs for organizations with legacy hardware). The features of Access 2010 used in conjunction with Sharepoint 2010 seem to me to be most compelling for and small businesses. I do not know if I could sell clients on hosted Sharepoint / Access. I have been able to sell clients on hosted Exchange, and it is been very said. All I would add is that most corporate IT departments will not deploy anything Access-based no matter what MS does to it. There is no question the pricing is
DataBase Access 2010 for software development Hi, What do I need to use Access 2010 (or perhaps 2007) to port our 2003 application and create an executable (MDE in Access 2003)? Are there any issues with 2010? -paulw You can use Access 2010 to develop your MDB until it is ready to release, but you will then need to use Access 2003 to create the MDE. - - Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users
DataBase Access 2010 with Sharepoint 2010 I found this article http: / / sharepointproconnections.com / Articles / tabid / 149 / nodeid to me was these two points: client." Hopefully this means you can test out the Access 2010 in a browser capabilities. 2.0 AA compliance. Level 1 browsers, which support 100 sharepoint. Just like now we build applications to the office standard (that might use outlook, excel, and MS access on the desktop), in the future we build applications that does all the similar functions figure out what is not going to work as well in the browser as in Access itself? Surely you are not claiming that 100% of an Access app is going to convert to the browser-based Sharepoint version and have exactly the electricity is knocking on our door step and it here to stay. . . - - Albert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal@msn.com Well, actually, yes I kind of am making have to choose a "web database" option for this to happen. When you do this access will restrict your feature set to web only features - - in fact this option even automatically
depende de qué uses, como, etc. . . ningún extremo está bien. Tu usas siempre relaciones desde access? saludos, Martín Hola amigos, me gustaría en esta ocasión abrir un debate para intercambiar opiniones si veo todas esas flechas me aclara el partido, pero no tiene porque ser en access!!! existen millones de herramientas para diseñar MER, y este entra dentro de las documentaciones, por pero entramos en un pt más discutido todavía. . si hay algo que lo puede hacer access (o la aplicación que sea) o yo. . .¿Qué preferis?. . .(sabiendo las ventajas / desvetajas que tiene nada ;-), pero estoy completamente en contra de que lo hagan así quienes están iniciándose en Access, pues es muy fácil que lo hagan mal, puede ser una fuente inagotable de problemas desde el principio? Si fueran sexuales habría que planteárselo ;-) - - Saludos José Bengoechea Ibaceta [MS-MVP Access] http: / / jbengoechea.com / http: / / jbchea.net Hola amigos, me gustaría en esta ocasión abrir un que acelerar o frenar, antes de salir de casa? - - Saludos José Bengoechea Ibaceta [MS-MVP Access] http: / / jbengoechea.com / http: / / jbchea.net buff, no estoy nada deacuerdo. . Si empiezas una base indices, tipos de campos, tablas que necesitas, etc. . . Además, las relaciones no son únicas de access, son una característica como son SQL Server, Access, Oracle, MySQL. . . . y que para eso se llaman así. Otra cosa es que no sepas
DataBase Considerations migrating from Access 97 mdb to Access 2003 (or up)? What are the things I need to watch for? I know about linked sheet properties and Sandboxing mode and making sure to run Jet 4.0 SP8 for 2003 but what else should I look for? We're kind of at the end of the road (so it seems) with Access 97. It does not play well with Windows 7 Professional even in XP Mode, the is crashy / unsreponsive at times. I figure moving up to a more 'modern' version of Access can help alleviate some of these problems and allow it to run native in Windows XP mode. So I am all ears for recommendations on migration or ways to get Access 97 to work properly in Win 7. Thanks a bunch. Hi Ryan. I have been for the developer, not quite so much for the user). You'd get used to 2003 in a few hours. XP mode is the only way I could see to install