volunteer organisation I work for, and just want to know if this is possible
to do with MS Access?
Basically, at the end of every month, each volunteer must hand in their
expense claims along with their monthly performance (hours worked etc...)
This is all currently done on paper.
Now, what would be ideal is for all of this to be done on a network-based
Database. So basically, each individual has restricted access to the
database and can enter their expenses and performance details and then this
can be authorised by a line manage (not too sure how you can electronically
sign off expenses). Then add the end of a month, the boss can simply print
out everybody's claims.
Is this possible to create in MS Access? It will be network-based and there
will need to be different levels of access (ie. restricted access for
individuals, semi-restricted access for line managers and complete access
for boss)"Neil Greenough" <neilgreenough@.btopenworld.com> wrote in message
news:ckj3au$72m$1@.hercules.btinternet.com...
>I am looking into some possible ideas to get rid of a lot of paperwork for
>a
> volunteer organisation I work for, and just want to know if this is
> possible
> to do with MS Access?
> Basically, at the end of every month, each volunteer must hand in their
> expense claims along with their monthly performance (hours worked etc...)
> This is all currently done on paper.
> Now, what would be ideal is for all of this to be done on a network-based
> Database. So basically, each individual has restricted access to the
> database and can enter their expenses and performance details and then
> this
> can be authorised by a line manage (not too sure how you can
> electronically
> sign off expenses). Then add the end of a month, the boss can simply print
> out everybody's claims.
> Is this possible to create in MS Access? It will be network-based and
> there
> will need to be different levels of access (ie. restricted access for
> individuals, semi-restricted access for line managers and complete access
> for boss)
This is an MSSQL group, so you will probably get a better response in an
Access group. Having said that, if security is a concern, you might want to
consider using Access as a front-end interface only, with all the data in
MSDE (a free, 'stripped down' version of MSSQL for small applications). This
would give better security, scalability and data integrity, but it would
also add complexity, so it depends on what skills are available in your
organization, and how important those features are to you. A good Access
implementation can be more useful than a poor MSSQL one.
http://msdn.microsoft.com/library/d...c_msdeintro.asp
Simon|||Apologies Simon.
I just thought that the subject of SQL servers kinda overlapped that of MS
Access.
Thanks a lot for the advice.
"Simon Hayes" <sql@.hayes.ch> wrote in message
news:416d175a_1@.news.bluewin.ch...
> "Neil Greenough" <neilgreenough@.btopenworld.com> wrote in message
> news:ckj3au$72m$1@.hercules.btinternet.com...
> >I am looking into some possible ideas to get rid of a lot of paperwork
for
> >a
> > volunteer organisation I work for, and just want to know if this is
> > possible
> > to do with MS Access?
> > Basically, at the end of every month, each volunteer must hand in their
> > expense claims along with their monthly performance (hours worked
etc...)
> > This is all currently done on paper.
> > Now, what would be ideal is for all of this to be done on a
network-based
> > Database. So basically, each individual has restricted access to the
> > database and can enter their expenses and performance details and then
> > this
> > can be authorised by a line manage (not too sure how you can
> > electronically
> > sign off expenses). Then add the end of a month, the boss can simply
print
> > out everybody's claims.
> > Is this possible to create in MS Access? It will be network-based and
> > there
> > will need to be different levels of access (ie. restricted access for
> > individuals, semi-restricted access for line managers and complete
access
> > for boss)
> This is an MSSQL group, so you will probably get a better response in an
> Access group. Having said that, if security is a concern, you might want
to
> consider using Access as a front-end interface only, with all the data in
> MSDE (a free, 'stripped down' version of MSSQL for small applications).
This
> would give better security, scalability and data integrity, but it would
> also add complexity, so it depends on what skills are available in your
> organization, and how important those features are to you. A good Access
> implementation can be more useful than a poor MSSQL one.
>
http://msdn.microsoft.com/library/d...-us/dnacc2k2/ht
ml/odc_msdeintro.asp
> Simon|||"Neil Greenough" <neilgreenough@.btopenworld.com> wrote in message
news:ckj8vn$elq$1@.hercules.btinternet.com...
> Apologies Simon.
> I just thought that the subject of SQL servers kinda overlapped that of MS
> Access.
> Thanks a lot for the advice.
<snip
No need to apologize - they're often used together, and many people do
associate them with each other somewhat, rightly or wrongly. Since this
group is an MSSQL one, you're unlikely to get responses to pure Access
questions; if you are using them together, then people here will generally
prefer solutions which rely on MSSQL functionality, not on Access.
Simon
No comments:
Post a Comment