General Access Questions

[phiednate]

I have been starting to learn the ins and outs of Access over the past week. However, being the novice, I have run into a few problems and dont know the correct this to search for. These are likely very simple questions but if you all could point me in the correct direction I would really appreciate it.

- I am building a database for some contract tracking at work. It is a military network but I have direct access to one of the servers so I think splitting the database is my best options. Is this the best type of a front end for my situation?

- So far, the only method of "customizing" the front end is to hide table and forms that the typical user won't use. I am sure there is a better and more attractive method out there but I have no idea what it is. Any ideas for a complete novice?

- Sharepoint was recently added to our network. Is this a reasonable option for me? I tried playing around with it and I cant seem to find a benefit with it vs. splitting the DB.

If anyone has some good resources for starting out please send them my way. Like I said before, I am a complete novice to this type of thing but the possibilities have kept me inetersted. Thanks for the help in advance!

-Nate

 

[pbaldy]

Yes, splitting the database is a good idea. The back end will be on the server, each user has a copy of the front end on their PC.

Most of us designate a form to be the form that starts up when the application is started, and hide the database window/navigation pane as well.

I haven't used SharePoint, but it sounds like Access will serve your needs quite well as the back end.

 

[phiednate]

Thanks for the help!

I was playing around with the Northwind example that came with Access 2007 and they had some interesting ways for displaying data. Looks like I got alot of research ahead of me.

Curiosity, it terms of design, is the Northwind example fairly extensive or with some time and learning would a novice like myself beable to create something similar? Just trying to guage how deep I am gonna have to get into Access to be able to accomplish my goal. Thanks!

 

[wazz]

i haven't looked at northwind for a long time but i remember it being fairly extensive -- for a sample db. a work(ing) db could easily be much bigger and/or more complicated; but not necessarily. (how's that? )

just want to add one important thing to read up on: Normalization. do it FIRST.
here are some links. i have a bunch saved and i'm not sure now which ones were the best; hopefully these are good ones:

http://www.deeptraining.com/litwin/dbdesign/FundamentalsOfRelationalDatabaseDesign.aspx
http://office.microsoft.com/en-ca/access/HP051884441033.aspx
http://support.microsoft.com/default.aspx?scid=kb;EN-US;209534
http://r937.com/relational.html

(the first one and last one might be the same article).

 

[gemma-the-husky]

business applications are often quite complex,

if you are starting why not try something you are very familiar with, and build a database about it

eg - a CD or DVD catoalogue
or if you play golf - a database to store courses/holes/scores - thats actually very informative and not too hard.