From: Stewart Berman on 11 Feb 2010 00:41 Access 2007 Where is the layout information for the Relationships window stored? Is it in an object and if so how do I reference it? Please note I am not talking about the relationships -- I know how to extract that. I would like to know how to extract the current layout in the Relationships window.
From: Allen Browne on 11 Feb 2010 03:37 It's stored in a table called MSysRelationships. To see it, right-click the Nav Pane, and choose Navigation Options Check the boxes for Hidden and System. Stephen Lebans has a utility that interprets this table, though it's not readable: http://www.lebans.com/saverelationshipview.htm If you just want to display more details about the fields on the relationships report, see: http://allenbrowne.com/AppRelReport.html -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Stewart Berman" <saberman(a)nospam.nospam> wrote in message news:du57n5lld8b00hm12ml5n1uo344pdlvofh(a)4ax.com... > Access 2007 > > Where is the layout information for the Relationships window stored? Is > it > in an object and if so how do I reference it? > > Please note I am not talking about the relationships -- I know how to > extract that. I would like to know how to extract the current layout in > the > Relationships window.
From: Stewart Berman on 11 Feb 2010 10:21 "Allen Browne" <AllenBrowne(a)SeeSig.Invalid> wrote: >It's stored in a table called MSysRelationships. > >To see it, right-click the Nav Pane, and choose Navigation Options >Check the boxes for Hidden and System. > >Stephen Lebans has a utility that interprets this table, though it's not >readable: > http://www.lebans.com/saverelationshipview.htm It is supposed to do what I want. I converted it to an .accdb and tried to use it to read the relationship layout in another .accdb and had a problem. Is throwing an error when trying to open the MSysObjects table in an external database -- no read access. Not sure why as the code to open the recordset looks identical to the code I use to do the same thing. It should not be hard to workaround. > >If you just want to display more details about the fields on the >relationships report, see: > http://allenbrowne.com/AppRelReport.html
From: Allen Browne on 11 Feb 2010 19:31 Sorry, I can't support you with Stephen's code, and he has moved on too. Not sure what else to suggest. I take it you're doing more than iterating the relationships themselves (which you can do via the Relations collection in DAO), and you're trying to ascertain which tables are displayed and where in the Relationships window. -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Stewart Berman" <saberman(a)nospam.nospam> wrote in message news:eq78n5p3d3226fbkoksv5p7tqvbbg026l9(a)4ax.com... > "Allen Browne" <AllenBrowne(a)SeeSig.Invalid> wrote: > >>It's stored in a table called MSysRelationships. >> >>To see it, right-click the Nav Pane, and choose Navigation Options >>Check the boxes for Hidden and System. >> >>Stephen Lebans has a utility that interprets this table, though it's not >>readable: >> http://www.lebans.com/saverelationshipview.htm > > It is supposed to do what I want. > > I converted it to an .accdb and tried to use it to read the relationship > layout in another .accdb and had a problem. > > Is throwing an error when trying to open the MSysObjects table in an > external database -- no read access. Not sure why as the code to open the > recordset looks identical to the code I use to do the same thing. It > should > not be hard to workaround. > >> >>If you just want to display more details about the fields on the >>relationships report, see: >> http://allenbrowne.com/AppRelReport.html
From: "Charles Wang [MSFT]" on 12 Feb 2010 00:35 Hi Stewart, To work around this issue, you can first import the hidden table MSysRelationships from your external database to your local copy and then read the local copy. Best regards, Charles Wang
|
Next
|
Last
Pages: 1 2 Prev: Creating a membership database Next: Ten calendar harm one of the products |