Collecting User Input

[S Jackson]

I have been tasked with designing a database that will be accessed by
several different groups of people. More specifically, there will be 11
different groups each wanting to view data relevant to them.

What is the best way of designing an interface to collect information from
the user in order to direct the system to display data based on their input?
Do I design a form that creates a query based on user input? Or can I
design a query with "Like" statements? I'm pretty confident I can design
the Query, but I'm not experienced nor trained (all my knowledge is
self-taught) enough to design the Form and write Code that generates a
query, and then displays the information via another form. But, I'll learn
if this is the best design.

Any input/opinions are greatly appreciated! Thanks in advance.
S. Jackson

 

[RobFMS]

In some cases, you may want to see how the user's are collecting the data
the old way. Are they using a standardize form? That may be a start on how
to design the form in Access.

FMS has a web page on book recommendations that may be of some interest:
www.fmsinc.com/toplevel/books.htm

Additionally, there are technical papers that might be of interested:
http://www.fmsinc.com/tpapers/index.html


HTH

--

Rob

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Problems with your database? Need to upgrade your application?
Contact the FMS Professional Solutions Group: www.fmsinc.com/consulting

Need a Book Recommendation?
www.fmsinc.com/toplevel/books.htm

Need software tools for Access, VB or .NET?
http://www.fmsinc.com
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

[Albert D. Kallal]

Are these users entering data, or do these users need to be able to create
reports?

While you are answering the above, here is some screen shots and some ideas
for helping your users with reports.

http://www.attcanada.net/~kallal.msn/ridesrpt/ridesrpt.html

 

[S Jackson]

Oh my! What wonderful information. Unfortunately, I am just not
knowledgeable enough to create these kinds of forms.

I should clarify that I am modifying an existing database that was designed
exclusively for our office to render it usable by a large number of
different offices.

So, I already have a database design (but it may require some
modifications).

Your reply made me aware of something that I have designed in my current db
that could be better. I have a report that lists the cases that have been
assigned during a "month." I wrote a query including this: Month:
Month([admin cases].[assigndate]) Like [Enter Month Using Numeric Indicator
eg 7]. When the user selects this report from the switchboard, the query
asks the user for this input. I can see how this is a bad design and it
bothered me when I created it because I knew it would create confusion for
the user as to how to enter the information being requested (07, 7, seven,
July, etc.). But, you've pointed out I could be using calendar controls . .
... hummmmm.... I wonder how long this is going to take me to figure out!
Sigh . . . back to the drawing board!


Thanks! S. Jackson

 

[S Jackson]

I'm sorry, also, in answer to your question, the users are entering data AND
creating reports.

S. Jackson

 

[Gil]

I just like to suggest that designing a FORM is not
difficult. Now you need to be simple in placing items on
the form. For example let's make the first item as "View
Data" . When people click it, you could have a drop down
menu for their selection again. You can have 11 (items)
groups. Let's say "Service". "Supplies",.....etc. In
summary design a query based on their inputs. Hope it
helps........from Gil Lopez