New User...create a traditional jet database or SQL Server and ADP

C

Cithindril

I'm a new Access user and have seen discussion that Microsoft will
discontinue support for traditional Jet SQL in future Access editions. I'm
intending to create an office database to track personnel data and don't
expect more than 3 users to have access. Would it be better to create a
traditional Jet database or should we develop an SQL Server-based system with
ADP's? I'd like the setup to be effective for at least 5 to 10 years but
would like to keep it fairly straightforward. Any advice would be greatly
appreciated.
 
J

Jeff Boyce

How old a vehicle would you drive? If it were 5-10 years old, and you
bought it new, would you be concerned?

If you are a new Access user, and have never used SQL-Server, you may wish
to start with something (Access/JET) you can have more direct control over.
The learning curve for Access is steep enough that you may not wish to add
the additional learning curve for SQL-Server. (nor the additional cost of
acquiring SQL-Server, Client-Access Licenses, a server to run it on, a
network support person plus a SQL Database Administrator, ...!).

You haven't described what kind of "personnel" data you are tracking, so it
isn't clear if you actually need to use a database at all.

Good luck

Jeff Boyce
<Access MVP>
 
B

Brendan Reynolds

Jet is not going to go away any time in the foreseeable future. I can't
guarantee that Jet will still be around in 10 years time - but then, I can't
guarantee that SQL Server will still be around in 10 years time, either.

If I were starting a new Access application today, it would be an MDB.

BTW: You don't have to use an ADP to use SQL Server. You can use an MDB as a
front-end to a SQL Server database via ODBC.
 
C

Cithindril

Thanks for the responses. To clarify, I currently work in the Human
Resources department of a moderately-sized company and need to track
personnel qualifications and transfers for approximately 1000 employees.
Inter-departmental transfers are fairly frequent and all of the data is
presently being tracked on a set of Excel spreadsheets. The manual process
of updating this data is quite tedious and error-prone so we're looking to
generate a reasonably simple relational database to manage the data. Based
on your advice here and discussions elsewhere, I think we'll start with an
Access MDB front end / back end and look at upsizing the back end to SQL MSDE
down the road if it becomes necessary.

Thanks again for the help and I'd like to hear any dissenting views if other
folks feel stongly the other way.
 
T

tina

no dissent, just a word (or two or three) of advice. your first post stated
that you're new to Access. because Access tables in datasheet view look very
much like Excel worksheets, many newbies make the potentially disastrous
mistake of assuming that Access is very similar, in function and design
approach, to Excel - it is NOT. Excel is basically a "flat-file" design,
while Access is based on the concept of relational data modeling.

the first, crucial step in building an Access database is to learn the
basics of relational data modeling. these newsgroups are full of questions
from folks who decided to skip that step (or didn't know they should have
taken it), and are now trying desperately to glue together a workable
structure on top of a flawed foundation (i wouldn't knowingly live in a
house built that way - would you?).

if you haven't already, i strongly urge you to take that all-important first
step. one good book that teaches relational data modeling concepts is
Database Design for Mere Mortals by Michael Hernandez. you can also find
numerous links to helpful information at
http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html
beginning with the Starting Out and Database Design 101 links.
this link is well worth bookmarking; i'd be surprised if there is a more
comprehensive list of resources in any one place on the web.

if you're already experienced in relational database design (using other
software, perhaps), then the above advice is not news to you. but maybe
it'll help someone else who reads this thread. :)

hth
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top