Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Where to create the relationship? 5

Status
Not open for further replies.

Storyteller

Instructor
Apr 19, 1999
343
CA
Hello All,
I have an Access application that has been split into FrontEnd and BackEnd databases. The BE holds only the tables and the FE holds everything else.

My questions is where do I create the relationships between the tables? Do I do it at the BE only or FE only or on both ends ;-)

Currently, I have the relationships created on both ends, but I'm not 100% sure if this is correct.

Thank you for your comments.

Regards,
Michael
 
Michael,

The data's in the back end, so that's where the relationships will need to be, if they're to be enforced when the data go into the table.

Jeremy

==
Jeremy Wallace
AlphaBet City Dataworks
Access Databases for Non-Profit Organizations

Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.
 
Hello Jeremy,
Thanks for the information. I'll give it a try.

Regards,
Michael
 
From my understanding of this plot so far, the original requestor needed to learn whether the 'Relationships' were "exported" to the "BE" database during the operation of the Data Splitting Wizard -- which I understood to be answered in the affirmative.

On a not altogether related topic, what if in addition to the tables which are split off from the "FE" database, the developer needs to add add'l tables to the database application--my hunch would be that they are built/stored in the 'BE' database and that then a 'Link' with that table is generated from the 'FE'.

Last question: what if there's an interest in 'turning back the clock' on the splitting process....can the 'BE' tables be reloaded into the 'FE' database?
 
I'm following up my 'reply' with another question of sorts....

I thought I would try splitting a database and once the process completed, I looked into the 'Relationships'. I learned that the relationships are to be found in both FE and BE databases (we're talking about A2K here in case it makes any difference). Is the point of the previous responders message that the developer needs delete the relationships from the FE, leaving them intact in the BE?
 
USC,

I don't see anything about exporting of relationships in the posts by the OP, so you may be thinking of a different thread.

That said, my guess is that the wizard would build the relationships in the BE just like they are in the FE. There's nothing wrong with having them in the FE, they're just not necessary.

Yes, new tables should be build in the BE and linked to by the FE.

Undoing the split is easy: delete all the linked tables in the FE, import the tables from the BE, and rebuild the relationships. Alternately, you could just import everything from the FE to the BE, and then you wouldn't have to rebuild the relationships.

Just make sure you make backups of everything before doing any of this.

Jeremy

PS: in general, it's best to start your own thread when you have questions, so that the focus can stay on the OP's topic, and not wander. Not at all a big deal, just thought I'd point it out for future reference.

==
Jeremy Wallace
AlphaBet City Dataworks
Access Databases for Non-Profit Organizations

Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.
 
Hello All,
Thank you for all your replies. I should have mentioned that I created the databases as seperate BE and FE. I then linked the BE tables to the FE.

When you create your relationships between the tables in the BE they also exist in the FE after you have linked the databases.

I have noticed something odd though. If you do not enforce referential integrity in the BE database you cannot do so in the FE. This would support Jeremy's reply. (Star to you)

Thanks for everyone's replies.

Regards,
Michael
 
In fact, enforcing RE in the FE won't do anything. There's no need to do this. I'm not quite sure why Access allows it, but I do know that it won't affect the data at all.

Jeremy

==
Jeremy Wallace
AlphaBet City Dataworks
Access Databases for Non-Profit Organizations

Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top