Need help with few things (Basic access questions)

[Strider]

I am making a simple database/game where the user can browse items in shops, buy them for their character, equip them, and have their stats increased accordingly, just by clicking different buttons. I will be needing some help now and then, when I encounter an obstacle, so I will keep this topic open until I'm done...



First I need to ask, is this kind of thing even possible? And with basic access skills (queries,reports,forms,macros) ?

I need to know if this is possible:
-Table Class (will show all available classes and their bonuses)
-Table Player (shows basic player info and base stats)
-Table Headgear(shows all available Headgear and their bonuses)
-etc...

My form "Player" will show player details,stats and equipped items. How can I create fields like "Intelligence" , which return a sum of base Intelligence field from table Player, sum of all Bonus Intelligence fields from all equipped items and Bonus Intelligence field from table Class? Is this even possible?

Is it possible to create a little menu with possible actions, like Buy, which takes you to another menu where you click on items you want to buy, which then decreases your amount of money by the cost of the item, updates your Inventory table and OwnedHeadgear table, and then you go to your Player form, click on Headgear slot, choose from one of your OwnedHeadgear, and then your stats get updated for the Bonus stats.

Thank you for your patience and thank you in advance

[June7]

Certainly all is possible, the how is subject to circumstances.

You have asked a lot of broad scope questions and to try and provide detailed guidance is not feasible.

Have you completed any tutorials (book or on-line)? You need a solid grounding in basic relational database principles, Access functionality, programming concepts, and macro/VBA coding.

Here is one tutorial site http://www.rogersaccesslibrary.com/

I think you will find this application you want to build is far from simple.

[ssanfu]

You need to be aware of reserved words.... should NOT have a table named "Class"; it is a reserved word.
Here is a list of reserved words: http://allenbrowne.com/AppIssueBadWord.html

And should not use spaces, punctuation, or special characters (underscore is the exception) in object names.


I would advise designing your dB in paper/whiteboard first.

* You can design your tables and check normalization and functionality.
* Then design your forms (sketch what they look like with controls)
* When you get all of this on paper (whiteboard), then start typing in the computer.