Too Many Record

[kernel76]

Hi I've a question for you (a problem for me!)
With Access 2000,
i've four tables A-B-C-D relationed with :
1A --> +B
1B --> +C
1C --> +D

Taking in example C and B:
All records of C must contain every record of B! but if B=500 record and C=700 I must carry c to 350000 records?
I’,m however successful to relationship the tables with one to many between B and C, but in C the id of B it is empty and therefore
if I try to add from the mask one record to c, it says to me that not there is a record correlated in b! it’s true! How can I resolve this problem?
Sorry for my english.
Thank’you very much for any reply!

 

[neileg]

Sorry but it's not clear what you want to do. However, I don't believe that whatever you are doing that you need to create 350,000 records.

Could you explain what the purpose of your database is?

 

[kernel76]

An example
_

I’ve got:
___________
TabellaB
Id_b (primary key)
1
2
3
____________

________________________________________
TabellaC
Id_c (primaryKey) Id_b CampoText
1 text
2 text
3 text
4 text



I WOULD LIKE TO DO THIS:

_____________________________
TabellaC
Id_c() Id_b Campotext
1 1 text
2 1 text
3 1 text
4 1 text
5 2 text
6 2 text
7 2 text
8 2 text
9 3 text
10 3 text
11 3 text
12 3 text
__________________________

 

[kernel76]

It does't well formatted

 

[neileg]

Thanks for the example. What you have illustrated is what I understood from your first posting.

But we need to know why you want to do this. I think that you may be able to get what you want with a query which will combine the data in the way you want, but only at the time you need it, so you don't have to store any data at all.

To give you a solution means that you have to explain the purpose. Don't worry about your English.

 

[kernel76]

thank' you very much neileg!
But may be i'll try with another solution.

 

[The_Doc_Man]

if I try to add from the mask one record to c, it says to me that not there is a record correlated in b! it’s true! How can I resolve this problem?

I'm not sure where you are going with this, but your immediate problem is that you must have tried to enter data to your C table, having established referential integrity on the B --> C relationship, without first entering a proper record in the B table. So of course, Access complains because that is a case where referential integrity is not being preserved.

If you have cascading referential integrity through four tables, you have placed a requirement on yourself to enter data from the "top" of your structure so that you CAN enter the data in the lower levels of the structure. In other words, you have created a logical structure that can ONLY be populated in a top-down methodology.

All records of C must contain every record of B! but if B=500 record and C=700 I must carry c to 350000 records?

These are maxima or perhaps you might prefer calling them practical limits. C would have 350000 records if and only if for every record B there existed 700 distinct records in C.

But there is no guarantee (from the Access viewpoint) that you need ANY records in C corresponding to a given record B. This is because the Access paradigm is a SPARSE (not completely populated) database. It only has the records it has, not the theoretical limit of those records. You don't have to represent any records in C just because you have a particular record in B.