Hey Jeff.
Thanks a lot for your support.
We do need start thinking change our strategy... I will talk to staff and
see other available options or to hire someone who could help us with
development.

B.Rgds,
MaurÃ*cio

"Jeff Boyce" escreveu:

MaurÃ*cio

I usually advise folks just starting out with Access that there are three
significant learning curves they'll need to be willing to take on if they
are to be successful using Access to develop an application.

1. relational database design -- if "normalization" and "relational" aren't
familiar terms, become familiar with them!
2. Access tricks and tips -- you'll need to learn the idiosynchracies of
how Access does things.
3. Graphical User Interface design -- what kind of design(s) work well for
users and what kinds work against users.

Oh yes, and you need experience as a developer!

If your situation doesn't allow the time or resources to handle all these
learning curves, you may need to consider hiring someone who has already
learned these.

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP




"MaurÃ*cio Paiva" wrote in message
...
Hi Jeff, good morning.
I apologize to give you this trouble.

We have 2 teams (pricing and sales) and they want to make sure
whenever an user updates its individual spreadsheet that it will reflect
to
DB in access or any other suggestion.
There are specific fields in the spreadsheet that must not be seen by
sales
team.

Just to give you an idea... the pricing team (4 people) will feed their
individual spreadsheet and the sales team will check for prices anytime a
customer asks for.

I am an infrastructure guy in the company and we hv no developers in
here...
that's why I am lost with this case.

Was I clear? Could I clarify the idea?

Thank you,
MaurÃ*cio