RELATIONSHIP - MORE THAN 32 - HOW?

[cuok]

HI!
I need to make relation (one to many) to more than 32 tables. but i got an error. how can i resolve it?

thanks friends.

 

[dawnd3]

Your question is pretty vague. What error did you get? What were you doing when you got the error? When you say you are trying to relate more than 32 tables are they all related to just one table?

Dawn

http://www.calliopeconsulting.net

 

[Steve101]

cuok,

I'm intrigued by the fact that you have 32 tables which relate to this table. I have never developed an application in Access that needed 32 entries hooks into a single table, and I've been writing systems for a long time. Can you explain what you're doing; perhaps there's a way to re-organise the data.

Perhaps you do have a genuine requirement for these relationships; at any rate, your reply will be interesting,

Cheers,

Steve Lewy
Solutions Developer
steve@lewycomputing.com.au

 

[Steve101]

Following, I have posted email from cuok; my response is in the post below it

Hi steve,
Thank you very much for answering my q. in tek. Forum.
The project i need to do is to build an Access data base that deal with clinic visit. the patient may visit the clinic more then one time in year, and there He/she will take more than 32 test (each test in one table).

From your answer i understood that i made mistake – how can i solve it? Is there more details i have send you?
Thanks a lot
Eliahu Cheers,

Steve Lewy
Solutions Developer
steve@lewycomputing.com.au

 

[Steve101]

cuok,

Your approach is incorrect, and that is why you are running out of relationships. From what you've told me, you can basically manage with five tables in your database:

Doctor
Patient
Test
PatientDoctorVisit
PatientDoctorVisitTest

Have a bit of a look at the above tables, and see if you can understand the various relationships between them.

I think that the problem with your current approach is that you may be confusing tables with records. In your example where a patient will be taking 32 tests on a visit, each of these tests should result in a separate record in the single PatientDoctorVisitTest table; not in separate test tables.

Hope this helps to clear things up.
Cheers,

Steve Lewy
Solutions Developer
steve@lewycomputing.com.au

 

[LittleSmudge]

But Steve, potentially each test could require an exclusive set of parameters to be recorded

Eg.
Test 1 Records Heart Rate and Red Blood Cell Count
Test 2 Records Blood Temperature and Blood Oxygen %
Test 3 Records Weight and Inside leg measurement
Test 4 Records Eye Colour and Colour Blindness test results
Test 5 Records Blood Sugar level and Lung capacity
etc.. ..
etc..


Simplistic I know - but you get the idea.
It could be reasonable to suggest that the fields for a certain test's results are relational. However, non exists between Blood Oxygen% and Eye Colour - so they shouldn't be in the same table.

As you can see cuok - we need more data in order to help you.

G LS

 

[Steve101]

LittleSmudge,
You're of course exactly right, and some further analysis would be required; My point really was intended aloing the lines that the Test/Sampling data should be analysed and normalised to produce a generic data model to represent the different test, samples and recording of results
Be well, Cheers,

Steve Lewy
Solutions Developer
steve@lewycomputing.com.au

 

[LittleSmudge]

So .. .. WE are in agreement Steve -

Now, where is cuok with the data !


G LS