New Database..Need help

[beccadawn0622]

I am a beginner with Access. I have taken one course and have gone through my
textbooks and I am still lost. My employer needs a database for reporting
lines keyed by operators, etc. I need help. I can create my initial table
by importing the data from our ordering system no problem, but I don't really
no where to go from there. Is there someone that can walk me through or
suggest a template. My data includes the following:
Transaction Origiantor, Order Type, Order Number, Order Date, Line number,
amount, reason code, and original order number
I have a second table that includes the transaction originator (this is
their log on id for our ordering system) and their first and last name, and
their supervisor.
I would like to have a button that someone could click on to run a report.
They should be able to enter a date range, a specific operator, or specific
supervisor and get a report on how many lines keyed and how many orders
keyed. Also another report that a date range can be entered that will
generate number of lines and orders by Order Type.

 

[Jeff Boyce]

It sounds like you are looking for general help building an application.
You'll find folks here in the newsgroups available to help with specific
issues, but since most of us are volunteering our time, you might not find
many who can devote the number of un-billable hours that a general
developement project entails.

I like to remind folks that there are at least three significant learning
curves in developing Access-based applications.

First, if you aren't familiar with the terms "relational" and
"normalization", plan to spend some time coming up to speed on these.
Access is a relational database, and works best if it's feed the proper
diet. Your current "ordering system" could be organized any way.

Second, Access, like any other tool, takes some learning on "how to" do
things.

Finally, Access is a power saw, not a bookcase (like Word and Excel). Most
folks never touch a "relational database" in normal life, and don't know (or
care!) about how to make it work. They just want help getting THEIR jobs
done. A really usable Access application hides the complexity of Access
from the user. "Easy ... is HARD!" If you don't understand graphical user
interface design principals, you could make something that no one wants to
use!

Are you prepared to devote the time needed to come up to speed on all three?

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[beccadawn0622]

Sorry if I wasn't specific enough. I am very capable of learning how to do
this on my own, I was hoping for direction more or less, I apologize if I am
wasting anyone's time. I have taken courses so I understand the general
concept but the textbooks are confusing me now. Maybe if I step away from it
for a day and come back to it, I can figure it out on my own.

I don't want someone to do the work for me.

Sorry again for bothering anyone.
=-)

 

[Jeff Boyce]

I certainly didn't take umbrage and folks here are not particularly shy, so
if you haven't heard back, don't worry about it!

Your original post mentioned creating a table from your current system. My
first point still stands -- unless you describe the table structure you
created from the current system, we don't have a way to assess whether the
relationally-oriented features and functions of Access will readily apply.

Your original post mentioned that you consider yourself a beginner, with one
course and the textbook(s). My second point refers to the myriad of tricks
and specific "how to's" to get Access to do what you want it to. Feel free
to post back with specific questions about how Access does stuff. That's
what the newsgroups are for.

Your original post described how you wanted users to interact with your
application ... and that was my third point.

Designing and developing an application will take considerably more
specificity (for you and/or the folks who help) than was available in the
general description you provided. If anything, that's probably a fourth
point -- how much experience you have with the application development
process.

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP