Looking for Table and Query design suggestions for Attached Database ..

[edmscan]

I have a Access 2010 database and I have attached it .. with sample data and I am looking for suggestions on Table design / Relationships / Indexes or anything that will make it work better.



The transmissions table .. actually has currently over 1 million records in it and will be growing .. so I want to make sure my design is sound. Radio.zip

I also have included the queries I will typically use. A couple of the queries will prompt for data criteria .. you can use 6429.

I think I have covered it all ... nothing is terribly broken just looking for design suggestions as the "transmission" table will be getting big .. so I want to optimize first before going forward.
I am far from an Access expert .. all suggestions are welcome.

Thanks
Kevin

[edmscan]

So this is how I look at it ... and may clarify things. This is for a communications system with radios / groups and transmissions.

The 3 tables are such ..

Kevin Table (really a radio table)
Radio - PK
User (1 per radio)
LastUpdate (1 per radio)

KevinGroup Table (really a group table)
Group - PK
Name (1 per group)
LastUpdate (1 per group)

Transmissions Table
Id PK
Transdate (1 per Id)
Transtime (1 per id)
Radio (1 per id) - FK
Type (1 per id)
TransType (1 per id)
Group (1 per id) - FK

However if you can see above ... there can be many transmission records for a radio (kevin table) .. and group (kevinGroup table).

I think I am normalized ... but am open to suggestions on improvements. I have posted my relationships below .. just to save downloading the database.

[June7]

Over 1 million records is too much for me to download the db file.

The relationships seem to be correct.

What is purpose of the db?

[edmscan]

Over 1 million records is too much for me to download the db file.

The relationships seem to be correct.

What is purpose of the db?

The attached DB only contains .. like very very few records, I just wanted to make it the same as the production one otherwise .. just with less records as that would not add anything here.

[June7]

Okay, for some reason the file was taking a long time to download on home computer.

Why is there an * character in the User values?

[edmscan]

Sorry .. I wish that my computer would tell me when someone replies in a better way.

I know it is weird .. but the * is there cause these are identified radios (designated with a * in the name) .. and ones without the * are unidentified. There are about 6400 identified ones and 300 or so unidentified.

[June7]

Why not a separate field for this status info? Can be a Yes/No field named Identified.

[edmscan]

Why not a separate field for this status info? Can be a Yes/No field named Identified.

Do you think there would be a performance difference if I removed the * from User in the Access table ? and did what you indicated. I can easily do it and quite likely will just cause I never use the imported data
in anywhere but in Access. The data never goes back into where it comes from.

I have a couple queries where I distinguish between the 2 .. and yes your way makes a lot of sense. I just do it this way .. as the data comes from a C application and it just works very well there.

I think something for me to do tonight.

[June7]

The Yes/No field will make it easier to filter records based on the status.