Print the database objects screen ??

  • Thread starter Thread starter David
  • Start date Start date
D

David

How can I print the screen I see when viewing - database objects - queies
(detail view)?

I have been using Print-screen but that gives me a bitmap. I want a real
printout or list to export.
 
There's no built-in feature other than the documenter which I believe
someone mentioned in another thread. You could write code to do it or check
out Total Access Analyzer from FMS (www.fmsinc.com).
--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.
 
Hi David,

In addition to Brendan's suggestion of using the built-in Access Documentor, you may want to try my
new "Doug Steele object Documentor" Add-In for Access. This add-in will create a nice report of all
your database objects for easy reference. The report will list all the objects by category in
alphabetical order in a three-column layout. It looks very sweet in my opinion and it's even easier
to use than the Access Documentor. Plus, you get a nice report saved in your database that you can
open again any time you wish! There is one version for Access 97 and another version that works for
2000, 2002, and 2003.

After installing, which takes all of about a minute to do, you simply do Tools | Add-Ins | Doug
Steele Object Documentor
That's it! Poof! A nice slick report created in your database in just a couple of seconds.

You can find the free Add-In on MVP Doug Steele's site here:

http://members.rogers.com/douglas.j.steele/Documentor.html

Hope you like it!

P.S. I also have a table documentor Add-in as well called the "John Viescas Table Documentor".
 
As in when the object was first created and when it was last modified?
Hummm...I suppose it could be done.
However, it might entail a big restructuring, but I'm not positive.

I'm not sure if the SQL statement that serves as the Record Source for the report could be modified
to include those two elements. This information may have to be written to a table and then fed into
the report. That is certainly feasible as I've done similar things for two other Add-Ins, but it
would be nice to only have the one report element.

I'll definitely do some research on this. Thanks for the suggestion!
 
MSysObjects has DateCreate and DateUpdate fields in it. However, I seem to
recall that DateUpdate doesn't work properly in newer versions of Access.
 
Hi Doug,

Yes, I saw that MSysObjects has those fields. And I seem to recall something about this not working
in later versions as well. It's been quite a while, but I *thought* it was something about
compacting would reset those values. Is this your recollection as well?

Do you think the SQL for the report can be modified to include those fields, or would it be
necessary to write those values to a table?
 
I don't remember compacting resetting the values. What would it reset to?

To be honest, I don't think there's a reliable way of including that info.
How would you determine when it was necessary to write those values to a
table?

--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)


Jeff Conrad said:
Hi Doug,

Yes, I saw that MSysObjects has those fields. And I seem to recall
Click to expand...
something about this not working
 
Hi Doug,

Sorry, poor choice of words on my part with "reset."
I thought it would change all the DateUpdated fields to the current date and time after a compact.
But, this is just my recollection and I could very well be mistaken. I'll probably run some tests to
be sure.

For your second point, I believe I know exactly what you are asking. Your Add-In only creates a new
report object which is *updated* so to speak every time it is open because your slick SQL just
queries the System Tables. There is no need to have this information stored in a table. Also, once
created the first time, there is no need to go back up to:
Tools | Add-Ins | Doug Steele Object Documentor
whenever you run the report. You just need to open it from the Database Window.

Now to see a difference, take a look at one of my other Add-Ins. You should still have a copy of my
"John Viescas Table Documentor" I believe. If you have not installed it, go ahead and install it and
then test it out. This Add-In creates a report AND a table in the database. The code loops through
all the tables gathering all the field information. It writes all this information to the table. The
report then uses this table as its Record Source. The information in the table is a "snapshot", if
you will, of the table structure for that moment in time. You can open the report again at any time
from the Database Window, but it will only be accurate up to the last time you ran the Add-In.

If you make any field/table changes and want to have an *updated* report you MUST go back up to:
Tools | Add-Ins | John Viescas Table Documentor
and re-run the Add-In. The table values will be cleared and re-populated with new information. So
this works different than your Add-In. Does that make more sense?

So if the SQL for your report could not be modified to include those two new values it is certainly
possible to write all this information to a table and base the report on that. I've done this before
so it is not a problem. This would of course make a fundamental change to your Add-In. My only point
was that I could easily do that, but naturally I prefer to just have the report instead of a report
AND a table. Follow me?
 
Hi Doug,

Sorry, poor choice of words on my part with "reset."
I thought it would change all the DateUpdated fields to the current date
and time after a compact.
But, this is just my recollection and I could very well be mistaken. I'll
probably run some tests to
be sure.
Click to expand...

This is correct. Got me this week. After a compaction modified and created
times are set to the time of compaction in A2003 for all forms (that db
doesn't have reports so can't check right now). Tables and queries are
preserved.
!!
hth
Marc
 
Hi Marc,

Thanks for the info, but now I'm perplexed!
I did a quick test on Access 2003 and the Date Modified did not change on ANY of the objects after a
compact! This is weird. Maybe this isn't such a good idea working these two values into the Add-In
(as Doug has already mentioned). More testing is definitely needed.
 
Hi,
Checking the db, I see it is A2000. Sometimes that automatic 'do you want to
convert' message was a better reminder, although generally glad it's gone.
Marc
 
Back
Top