Relationships view in fe

[Cutthroat]

I recently split a db that is still in development (A13). Overall, things generally seem to be working well. I had to add several new tables to the design and did this in the back-end where I also defined the new relationships for these tables. However, when I try to view the relationships in the front-end, I cannot see any of the pre-existing relationships nor do I see the new tables I added (or their newly created relationships). Everything looks great from the back-end, not so w/ the front-end though. BTW, I've also tried the show 'All Relationships' and 'Direct Relationship' operations w/ zero effect. The relationships view is super handy when I work w/ my beta testers as they are remotely located and we frequently reference the relationships view to discuss changes to the db structure. Why doesn't this view update w/ changes made in the back-end? Is this normal? Why wont the pre-existing or new relationships display? I understand the front-end is not where the magic happens, but it doesn't seem right that I can't at least see what I see in the back-end. Any insight would be greatly appreciated, thx.

[ItsMe]

I am not very knowledgeable with the Relationships thing in Access. I just do not use it or rely on it. Having said that, you can make changes to you backend file via the Relationships Window and save them so you can see them in the Backend. Then, from another Access file, you can import the Relationships defined on another file.

Using the Import Wizard, you can use the Advanced Options to include Relationships.

Whether or not this helps you and your current situation with linked tables, I do not know.

[Cutthroat]

I did that when I split the db, all relationships are visible and correct in the back-end, but like I said, none are visible in the front end. I linked my new tables and brought them into the relationship view thinking maybe that would work, but unlike in the back-end, it dd not automatically create the relationship, it only added the table to the view w/out any relationships visible like the other tables. Thx for your suggestion, I hope others can continue shed more light on the issue.

[ItsMe]

I think it is as simple as there are not any tables to manage. You have only linked tables in your FE file and, therefore, no tables to manage.

[CJ_London]

relationships are what they say they are - managing the relationships between tables, the primary one in my view being that a one to many relationship prevents orphan records being created and a secondary one which provides a map of the schema. Consequently they only need to be managed once - in the database where the tables resides. If you try to create relationships in the front end you cannot create a one to many type relationship. I do think people get confused between relationships and joins in queries - they look the same but have different purposes, just as the datasheet view of a table or query look the same, but they are different things.

[Cutthroat]

That makes sense, I just wish there was a way to include this view in the front-end for reference. Thanks again

[Cutthroat]

That makes sense, I just wish there was a way to include this view in the front-end for reference. Thanks again

[CJ_London]

if by 'for reference' you mean when you build queries the joins are already created for you, you can set a relationship in the front end, but not one to many. Takes a bit of time to recreate. Otherwise - do a printout of the relationships from the documenter. In a query, the one to many relationship notation is irrelevant, it has no impact on the query design or performance in any way.