Elmobram22
Registered User.
- Local time
- Today, 10:19
- Joined
- Jul 12, 2013
- Messages
- 165
When I remove the added parameter it works again without asking for TblResident.ID
query to only show if ID is matching in other table
- Thread starter Elmobram22
- Start date
Elmobram22
Registered User.
- Local time
- Today, 10:19
- Joined
- Jul 12, 2013
- Messages
- 165
My sincere appologies I thought you'd been working on the second file I uploaded. Hence the info was a little different. Your fix works beautifully without the need to change all the tbl info. Thank you so much!!!!!!!!
- Local time
- Today, 10:19
- Joined
- Feb 19, 2013
- Messages
- 17,493
well, Elmobram hasn't really set any relationships and there are a couple of lookup tables which could be simplified as they stand at the moment (tblCcoRole and tblHouse).
I also can't see the relationship between some of the tables, but given this is a cut down db and the OP says 'I did this database when I was learning so I know the data isn't the way it should be' I'm not surprised.
tblResMed should perhaps be broken down into two tables....
I can't see any fields called 'name' although use of spaces in field names and a lack of consistency in naming conventions makes for more work. Similarly, using the dreaded lookup in table design and possibly wrong data types (e.g. text fields holding numeric values) could create problems further down the line.
So I think my answer has to be that without knowing the full business process, I don't think it is for me to say.
What problems do you see?
I also can't see the relationship between some of the tables, but given this is a cut down db and the OP says 'I did this database when I was learning so I know the data isn't the way it should be' I'm not surprised.
tblResMed should perhaps be broken down into two tables....
I can't see any fields called 'name' although use of spaces in field names and a lack of consistency in naming conventions makes for more work. Similarly, using the dreaded lookup in table design and possibly wrong data types (e.g. text fields holding numeric values) could create problems further down the line.
So I think my answer has to be that without knowing the full business process, I don't think it is for me to say.
What problems do you see?
Elmobram22
Registered User.
- Local time
- Today, 10:19
- Joined
- Jul 12, 2013
- Messages
- 165
I agree it is wrong in terms of how I now make databases. I no longer use lookups and all my fields have no spaces and pk or fk and do work on relationships before creating any queries etc. as I say I learned to do what I do now building this and it's a very simple application so there is no real need to go into that depth but thanks for your input. When I have time I'll probably rebuild it from the ground up but I was just trying to create a quick fix which CJ enabled. Thank you for your input guys!! 
RainLover
VIP From a land downunder
- Local time
- Today, 19:19
- Joined
- Jan 5, 2009
- Messages
- 5,041
CJ
You approach is different to mind. not wrong just different.
I like to see a page with the full relationships including lookups.
This gives me a pictorial view of what is happening.
The use of "name" was within a full name only it had a space. eg "My Name". I was mislead by this. Sorry about that but no harm was done.
You approach is different to mind. not wrong just different.
I like to see a page with the full relationships including lookups.
This gives me a pictorial view of what is happening.
The use of "name" was within a full name only it had a space. eg "My Name". I was mislead by this. Sorry about that but no harm was done.
Similar threads
