Question Need help! Access beginner here!

[Joshin]

Hello, I was wondering if someone could help me with a little project. I am not very good at access but would really like to specifically figure out how to do this in either 2007 or 2003.

Basically what I want to do is create a form that essentially does the same thing as ATI's driver selection database

http://support.amd.com/us/gpudownload/Pages/index.aspx

Thank you very much ahead of time!

I have my own categories and such to put in, but I really do want to learn how to put it in that type of format

 

[pbaldy]

Basically cascading combos but with listboxes:

http://www.baldyweb.com/CascadingCombo.htm

 

[Joshin]

Basically cascading combos but with listboxes:

http://www.baldyweb.com/CascadingCombo.htm

Thank you very much! I have a few more questions, if possible.

How would I make it so I could make a "OK" button precede to the desired record whch has a lot of values of it's own? Like say, from that example, I pick NV then Vegas and there was a OK, where it would bring up another form that would display data such as population size, or city area?


And one last question, how would I be able to make a change log so if someone edited say population size from 1,312 (example) to 1,532 it would display a window saying

"You are changing the value from 1,312 to 1,532"
Under that message would be a text box to enter "reason" for doing so
and under that would be another text box to enter the changer's initials for identifcation

How would you be able to store all that information, including the original and new values along with the time and date they were changed, aswell as the reason and the initials of the person who changed them?

 

[pbaldy]

You can use something like this to open a second form to a particular record or group of records:

http://www.baldyweb.com/wherecondition.htm

For the second, you may want to search on "audit trail", as there are numerous methods. The 2 most common are probably a memo field in the same table as the data with an accumulation of all previous changes, and a separate audit table with fields for field changed, value before, value after, etc. I like the second, but it's probably personal preference.