usability issues

[reema via AccessMonster.com]

What are the usability issues for new users in using Microsoft Access

 

[George Hepworth]

Perhaps you could start by defining what you mean by "usability issues"?

 

[reema via AccessMonster.com]

usability issues mean what are the problems in using Microsoft Access

 

['69 Camaro]

Hi, Reema.

usability issues mean what are the problems in using Microsoft Access

What problem are you having? If you describe what you want to do in Access,
we can probably give you instructions that will help you succeed.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[reema via AccessMonster.com]

well I am doing a reseach for new users using Microsoft Access ,my focal
point is usability of microsoft Aceess, so for that I am trying to write
every thing what new users can face, like what problems they will have if
they don't go through a right channel.

 

[John W. Vinson]

well I am doing a reseach for new users using Microsoft Access ,my focal
point is usability of microsoft Aceess, so for that I am trying to write
every thing what new users can face, like what problems they will have if
they don't go through a right channel.

Sounds like this could be a fairly thick book: how NOT to use Access. Isn't it
a bit presumptuous to ask unpaid volunteers to write it for you!?

John W. Vinson [MVP]

 

[reema via AccessMonster.com]

well Iam just doing a survey

Sounds like this could be a fairly thick book: how NOT to use Access. Isn't it
a bit presumptuous to ask unpaid volunteers to write it for you!?

John W. Vinson [MVP]

 

[reema via AccessMonster.com]

well Iam just doing a survey

Sounds like this could be a fairly thick book: how NOT to use Access. Isn't it
a bit presumptuous to ask unpaid volunteers to write it for you!?

John W. Vinson [MVP]

 

[reema via AccessMonster.com]

well Iam just doing a survey

Sounds like this could be a fairly thick book: how NOT to use Access. Isn't it
a bit presumptuous to ask unpaid volunteers to write it for you!?

John W. Vinson [MVP]

 

[reema via AccessMonster.com]

well Iam just doing a survey

Sounds like this could be a fairly thick book: how NOT to use Access. Isn't it
a bit presumptuous to ask unpaid volunteers to write it for you!?

John W. Vinson [MVP]

 

[reema via AccessMonster.com]

well Iam just doing a survey

Sounds like this could be a fairly thick book: how NOT to use Access. Isn't it
a bit presumptuous to ask unpaid volunteers to write it for you!?

John W. Vinson [MVP]

 

[reema via AccessMonster.com]

well Iam just doing a survey

Sounds like this could be a fairly thick book: how NOT to use Access. Isn't it
a bit presumptuous to ask unpaid volunteers to write it for you!?

John W. Vinson [MVP]

 

['69 Camaro]

Hi, Reema.

well I am doing a reseach for new users using Microsoft Access

So it's a homework assignment. We can't do your homework for you, but we
can point you in the right direction.

I am trying to write
every thing what new users can face, like what problems they will have if
they don't go through a right channel.

Your topic is much too broad. Literally millions of things can go wrong
when a new user who hasn't been trained to use Access takes the wrong steps.
I suggest you narrow down your topic to describing the problems that arise
when a new user approaches one specific area without training, such as
normalizing tables. If the tables aren't normalized before starting to
build the rest of the application, insertion and deletion anomolies will
creep into the application and data integrity is at risk. Any good
relational database theory book will show you examples of these anomolies
and how the integrity of the data is compromised.

For other suggestions, O'Reilly has a book series called "Annoyances," which
includes one for Access titled "Fixing Access Annoyances." Go to your local
bookstore or public library and take a look at it. It will probably give
you plenty more ideas to help you narrow your topic down to just one of
them.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[Brendan Reynolds]

The question is just too vague, Reema. You'll need to be more specific.

 

[David W. Fenton]

Literally millions of things can go wrong
when a new user who hasn't been trained to use Access takes the
wrong steps.

I'll bet there's one mistake that they make far more often than any
other: treating Access tables like a spreadsheet.

But that's not really what I'd consider a "usability" issue. It's
more a conceptual one.

 

[Guest]

Sounds like a first day in class question. What text book is your class using?

 

[Guest]

So it is a homework assignnment.

 

[reema via AccessMonster.com]

this is my research project in which I am researching different thoughts from
different people

 

[reema via AccessMonster.com]

how many times should I say this is not a home work question, if you all dont
want to help me in my research project just write cannot.
My reseach project is Usability of microsoft Access for new users, in which I
have to reseach so much.

 

[reema via AccessMonster.com]

can you say some

I'll bet there's one mistake that they make far more often than any
other: treating Access tables like a spreadsheet.

But that's not really what I'd consider a "usability" issue. It's
more a conceptual one.