Re: Is this possible??
- From: Shanin <Shanin@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 21 Sep 2007 08:24:02 -0700
I was thinking SQL from the get go just due to the size it may become,
although I've never worked in that. You may not know the answer, but is it
hard to convert a backend Access table to SQL?
I also looked at Access 2007 and some of the features seem to be what may
work for the frontend, such as the clicking on info in a report to open a
form. We are thinking of upgrading our software anyway since it's been a
while. Reading about the lack of security in A07, I think we'd probably want
to go to a backend SQL anyway to secure the tables since we wouldn't want
every user to be able to access wage information of employees. Thanks for
the info
"Pat Hartman (MVP)" wrote:
For starters, if you're going to do this, you would need to keep the data in.
Access and from Access, produce any Word or Excel documents needed for
reporting. If the data comes to you from many places or people, you can use
Outlook Forms or Excel workbooks to gather the basic data and then import it
into Access. It is possible the much of the saving of documents can be
dispensed with once the data is in a single place.
Access can handle millions of rows if each row is not very large. If the
actual data is too large for Access or if you have too many concurrent users
(over ~ 25), you can use SQL server or another RDBMS as the back end while
still using Access as the front end.
It is seven years and three versions since A2K was released. Microsoft will
be discontinuing support for A2K in the not too distant future. It might be
time to upgrade to A2003 while copies are still available. Converting to
A2007 is a huge change due to the complete recreation of the user interface
and your company might not want to spring for the training involved with
that.
"Shanin" <Shanin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AC4B0474-1945-4091-A4CF-FF2507413A20@xxxxxxxxxxxxxxxx
I have a co-worker that would like me to build a database that centralizes
a
huge amount of data and am wondering if Access would even be the avenue to
try and do this in. My thoughts initially are this would be a huge
undertaking and would probably lead to a swollen database and would be
better
served by something other than Access.
What they want is this, a database that they can click on a client's name,
where this would pull up a main screen which would show who worked for
that
client, and several other options like med errors for this person, the
person's budget, the person's plan and even being able to click on the
staff
that work for the client and being able to view their trainings, schedule,
etc. The main problem I see in all of this is all of this stuff is in
numerous different applications. All HR/staff trainings, employee
information is in an Access Database I already built. Schedules are in a
FoxPro database which also is our timekeeping system. I have our HR
database
linked to that to pull schedules so that is not a problem. Budgets,
errors,
etc, these are under the clients folder on a server and are in Excel and
Word, some are even still in Lotus. The part I would find hard is the
budget
forms come from the State and have to be in that form and you have to hav
a
new on every month, sometimes more than one if an amendment is made so you
would have a hard time trying to link to something where the file name
would
be constantly changing.
Without a total re-work of the agency on how things are reported, I don't
see this as being possible and even then, I don't think Access would be
the
best solution to store that much data.
Any thoughts?
- Follow-Ups:
- Re: Is this possible??
- From: Pat Hartman \(MVP\)
- Re: Is this possible??
- References:
- Re: Is this possible??
- From: Pat Hartman \(MVP\)
- Re: Is this possible??
- Prev by Date: Re: How to stop the combo box from repeating values
- Next by Date: Re: Automatically calculating age
- Previous by thread: Re: Is this possible??
- Next by thread: Re: Is this possible??
- Index(es):
Relevant Pages
|
Loading
