Table relationship in front end?

ricardofbarreiro

Registered User.
Local time
Yesterday, 22:38
Joined
Jun 19, 2014
Messages
17
I was creating a form by form wizard that has fields from 3 tables that is located on my back end db. When I finished the process, it informs that I don´t have relationship between the tables and then I was dropped in mey front end relationship tab.

These tables are all related in my back end db, why is that happening? :banghead:
 
The Relationships are in the backend where the tables reside. So, as long as you have linked to those tables you should have no problem. Are you showing those linked tables in yout front end?
 
A form is most often associated with one primary table. In this case Access is trying to figure out how to relate the data in the tables. My suggestion is that you create an unbound master form and the three unrelated subforms for the tables, provided the data in the three table are all unrelated...
 
The Relationships are in the backend where the tables reside. So, as long as you have linked to those tables you should have no problem. Are you showing those linked tables in yout front end?

In my front end db, my tables arent related, but on the back end are all related.

I tried to delete my linked tables on the front end, and link again from back end, but didnt work.
 
Last edited:
Hmm, I think we are not understanfing each other. When you split a database, they *talk* to each via the linked tables in the Front end. So, when you look at the Tables section in the Navigation Pane you should see your Tables with little arrows next to the Table icon. If that is not the case then...

1. What do you see for Tables?
2. If there are no Tables, how are you linking the Front end of the database to the Back end?
3. How did you split your database?
 
Hmm, I think we are not understanfing each other. When you split a database, they *talk* to each via the linked tables in the Front end. So, when you look at the Tables section in the Navigation Pane you should see your Tables with little arrows next to the Table icon. If that is not the case then...

1. What do you see for Tables?
2. If there are no Tables, how are you linking the Front end of the database to the Back end?
3. How did you split your database?

I see my tables with little arrows next to it. I split tables by the access database split button.
 
Okay, did you move the backend? Can you open the Tables. If yes, then the three tables you are trying to use, how are they related to each other?
 
Okay, did you move the backend? Can you open the Tables. If yes, then the three tables you are trying to use, how are they related to each other?

Yes, I move it all to my notebook to continue working on it. I delete my linked tables (with little arrow) from my front end, the linked it all again. I made same other basic forms, using only 1 table. These 3 tables are related 1 to 1 .

Table 1
IdProduct pk
more 10 fields

Table 2 (related from table 1 idproduct)
IdProduct pk
more 42 fields

Table 3 (related from table 1 idproduct)
IdProduct pk
more 42 fields

All relations made on my backend db.
 
Umm, not sure I understans how IdProduct is a PK in all three tables, this could indeed create a problem. I would suggest trying to build a query with all three tables and see if that works first.

However, please provide more details because normally only one table would contain the PK and the others would be FK's. Maybe if you give us more information on what the tables fields actually are...
 
I created a query on my backend and it works, with all three tables.

When I try to make the same thing on my front end, I can´t.

I will use FK on table 2 and 3, you are right on that.
 
Then something is wrong because it should also work in the Front end. Can you open the tables in the Front end? I would also try refreshing the links.
 
Then something is wrong because it should also work in the Front end. Can you open the tables in the Front end? I would also try refreshing the links.

I think I discovered this in the net:

"Rebuilding your file by importing everything into a new database is quite quick. The most time consuming part is laying out your relationship diagram again after every import. To avoid that problem, Stephen Lebans has a free utility to save and restore relationship views."

When I delete my linked tables in front end db, I lose my relations on it.

It´s corrupted now. Am I right? I will try this:

www . lebans.com / saverelationshipview . htm

What do you think?
 
Again, the relationships are not in the Front end they are in the Backend. Have you tried to open those tables? Do they open?

Deleting and recreating Linked Tables has no effect on the Relationships. This would only make a difference if you were not dealing with a Linked Backend.
 
Based on post number 8 there seems to more than meets the eye as far as 'issues' with the table schema hence worrying about relationships would probably be fruitless in the end...
 
Yes, I can open my tables from frontend and backend.


For instance:

I just make a new db, with 2 tables. Made a relation between them.

Split with Access Database Split button.

Open relations on front end , and the relation is there. On front end.

On backend is too.

When I delete my linked tables on frontend, and link again, the relation came to my frontend.

Why Do the db that I am developing, isnt importing relations like my example a just did? Corruption?
 
@Ken,

The OP did correct that with Table 2 and 3 are FK's not PK's, so I'm thinking they are okay. Oh, and also that the query in the Backend works as expected. I am concerned that the Links are actually broken which is why it's not working in the Frontend.
 
Based on post number 8 there seems to more than meets the eye as far as 'issues' with the table schema hence worrying about relationships would probably be fruitless in the end...

Yeah, maybe I just need to make only 1 table with this 100 fields.

That´s ok, but, why relations is not working properly on my front end db?
 
@ricardofbarreiro,

Well, I'm stumped and have to believe you have some sort of corruption. Don't know what else it could be. Seems like you're going to have to rebuild the front end.
 
Yeah, maybe I just need to make only 1 table with this 100 fields.

That´s ok, but, why relations is not working properly on my front end db?

If you are willing I'm sure if you posted the entire table schema experienced people here can help. Probably no reason for a hundred fields :)
 
Ok, I will try to show.

I work in a factory that manufactured each product goes through a quality control with 42 checked items required. Each item can have 3 status:

approved, disapproved or not applicable.

In case any of these items are disapproved, there is a second check of all 42 items compulsorily. If a new failure occurred a third scan begins. (never happened).

Well, I thought I'd create 4 tables. 1 table for the product plus 3 tables for each scan.

The relationship between the tables check the product ID.

That´s it.

I am from Brazil, strong with portuguese, weak in english...:D
 

Users who are viewing this thread

Back
Top Bottom