Starter question

[martijn1986]

Hi Micron,



Not sure if I understand the first part of your answer.

But yes this is a private database. So I guess adding options in the base tables like Park, Attraction Type, Attraction and RideOption can be done manually.
In that case I would only require something to keep track of my actual visits.

Preferably I would like to register the following:

date field: tblVisitPark - DateVisit
dropdown: tblPark-ParkName
dropdown: tblAttraction-AttractionName
dropdown: tblRideOption-Option (only when tblRideOption-AttractionID is equal to tblAttraction-AttractionID)


One more additional question not sure if I did right to do so but I added a column AttractionID to the tblVisitAttraction it felt like it was missing

[Micron]

When lookup tables are used to provide combo lists with options, one method is to use the NotInList method, which avoids having to use a form

By that I was referring to a form just used to populate the lookup table. Obviously if you are using a combo on a form, you are using a form, but that would be your data entry/edit form. If you don't know what NotInList is then you can look that up.

I haven't been following this thread in any detail - just commenting on populating lists for controls and whether or not you should/must use forms for that purpose. I'd have to start reviewing from the beginning before I could comment on your design.

[xps35]

Hallo Martijn,

You can do without the ride option table, but I think it is a bad idea. Your excel sheet shows why. You must store the name of the attraction multiple times in the combined attraction/rideoption table. Having that one table also makes stats on attraction level more difficult.

You do not need (and should not) store the attractionID in the table visit attraction. Just the ride option is enough. Because of the relationship between ride option and attraction, you are able to find the (name of) the attraction. That is how relational databases work.

[martijn1986]

Thanks for the feedback.

Yet again I'm amazed on how much I still have to learn on Access and database related stuff.
I'm still figuring stuff out it's fun to learn on the go.

I will diver a bit deeper in the forms to be build and how to make it as intuitive as possible and easy to access also on the go when I'm actually in the park.
I will also remove the Attraction ID option as proposed I think I understand what you mean.

End goald would be to someday create some application and link it to the database I did some programming in the past (in Visual Studio) but tbh it never was my strongest point.
That would be the ulitmate thing for the future I think

I'm still open to anything in terms of help or learning points, I'm still intrigued on how it works so take all pointers to learn and get better in Access/Databases.

[Micron]

Maybe some of these links would be helpful
https://www.accessforums.net/showthr...773#post521773