Relationships Report: how to print additional info about the fields

[Allen Browne]

New article at:
http://allenbrowne.com/AppRelReport.html
describes how to show information about the fields when you print the
Relationships Report in Access 2000 and later: the field type, size,
indexes, properties, and the number of records in the table.

 

[Arno R]

New article at:
http://allenbrowne.com/AppRelReport.html
describes how to show information about the fields when you print the
Relationships Report in Access 2000 and later: the field type, size,
indexes, properties, and the number of records in the table.

Very, very nice Allen !!

At my place (Dutch versions of Access) it works with Access 2003 but not with Access2000.
My first guess is that this is due to localizing ussues with the sendkeys command that you have to use with A2k.
Need to invest this more and adapt that code a bit.
No time for that at the moment but it won't be a big problem.

But as I said: This is very nice work!!
Very handy in a new project where I need to document a database.

Thanks.
Arno R

 

[Arno R]

Some follow-up (found some time to check...)
I only need to adapt the Sendkeys command to SendKeys "%BR", True and it works with A2k ..
(In Dutch 'File' is called 'Bestand')

BUT unfortunately there is an issue with the relationships report...
This has *nothing* to do with your code Allen, but it seems to me there is a bug in the Relationships-report Access provides.

I just found out that when we have a 'scrollbar-table' (not all the fields are visible) in the relationships-view, we might have a problem with the relations that are shown in the report.
The problem shows up when there is a relation to the second or third field (in the fieldorder that is) AND we do *not see* the *first* field in this 'scrollbar-table' (e.g. we scrolled down the list). Also: we still have to see the field that is part of the relation.
-- So let us say that we have a relation from a field in table1 to field number5 in table2
this field number5 is visible as the second field in the view ...
-- In that case the report presents a FALSE relation to the second field ....
Or
-- Let us say that we have a relation from a field in table1 to field number2 in table2
this field number2 is visible as the first field in the view ...
-- In that case the report presents a FALSE relation to the first field ....

I don't know if this is a known bug, but I just thought I would mention this here.
Solution: Make sure the *first* fields in the various tables are always visible in the relationships-view.

Arno R