To Access or not to Access?

[Guest]

I need to build a database application for tracking of rental equipment,
repairs, inventory, etc. I built a fairly powerful database several years ago
using Paradox 4 (DOS), but have not had experience with any other database
apps. I want my new application to be windows based, networkable for several
users at a time and possibly using the www as a front-end. Is Access a good
choice for this? Any suggestions would be appreciated.

My first glance at Microsoft's site I did not see any prebuilt example
applications. Any ideas where I can find examples?

 

[Guest]

Hi, Andy.

I want my new application to be windows based, networkable for several
users at a time and possibly using the www as a front-end. Is Access a good
choice for this?

Probably, but the ultimate decision needs to be based upon a number of
factors. Access is designed for a multiuser, networked environment on a
Windows platform. Theoretically, up to 255 users can access the database
simultaneously, but network, database design requirements, organizational
requirements, and database developer skills may limit this to as few as 1 or
more than 200. Most often, the range is from 10 to 30 users, but obviously
YMMV for your particular database needs.

One of the major pluses is rapid application development, especially for
experienced Access developers. Shorter development time leads to cheaper
application development costs, which is also a major plus. (I highly
recommend finding a knowledgeable Access developer to help you, because it
will shorten a very steep learning curve if you have anything complex that
the built-in wizards can't handle.) The built-in wizards can handle a lot of
development tasks, but not all. Access is also much cheaper to develop,
deploy and maintain than most client/server databases.

On the downside, poor networking equipment and intermittent power losses can
wreak havoc on Access databases, causing database corruption. If security is
needed, then don't use a file-based database, such as Access or Paradox, but
a client/server database, instead. Access also isn't good for the Web,
because anyone who can connect to the database file via the Internet can copy
the database file, replace the database file, or just make modifications to
the database file. You probably won't like what an unauthorized developer
(i.e., hacker) might do to your database behind your back.

My first glance at Microsoft's site I did not see any prebuilt example
applications. Any ideas where I can find examples?

There are quite a few on Microsoft's Web site, as well as others'. You may
download the Northwind sample database in Access 2000 format from here:

http://www.microsoft.com/downloads/...72-8dbe-422b-8676-c632d66c529c&displaylang=en

You may download the Orders and Developer Solutions sample databases from
here:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/bapp2000/html/mdbdownload.asp

You may download many database templates from here:

http://office.microsoft.com/en-us/results.aspx?Scope=TC&Query=database

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)

- - -
When you see correct answers to your question posted in Microsoft's Online
Community, please sign in to the Community and mark these posts as "Answers,"
so that all may benefit by filtering on "Answered questions" and quickly
finding the right answers to similar questions. (Only "Answers" have green
check-marks.) Remember that the best answers are often given to those who
have a history of rewarding the contributors who have taken the time to
answer questions correctly.

 

[Guest]

Thank you! Do you have any Access book reccomendations? I also made other
comments below if you care to respond.

Hi, Andy.


Probably, but the ultimate decision needs to be based upon a number of
factors. Access is designed for a multiuser, networked environment on a
Windows platform. Theoretically, up to 255 users can access the database
simultaneously, but network, database design requirements, organizational
requirements, and database developer skills may limit this to as few as 1 or
more than 200. Most often, the range is from 10 to 30 users, but obviously
YMMV for your particular database needs.

We will probably never have more than 6 (if that many) accessing the
database at the same time.

One of the major pluses is rapid application development, especially for
experienced Access developers. Shorter development time leads to cheaper
application development costs, which is also a major plus. (I highly
recommend finding a knowledgeable Access developer to help you, because it
will shorten a very steep learning curve if you have anything complex that
the built-in wizards can't handle.) The built-in wizards can handle a lot of
development tasks, but not all. Access is also much cheaper to develop,
deploy and maintain than most client/server databases.

There are a few classes taught through our IT department. I'll start there.
I'm going to have to invest the time myself unfortunately. An estimate for
what I need from a developer as $50k+. Whatever app I decide to use I realize
the road is going to be long. I'll start with the basics and add
functionality as I have the time.

On the downside, poor networking equipment and intermittent power losses can
wreak havoc on Access databases, causing database corruption. If security is

As far as the havoc wreaking goes, is the database usually repairable or do
I have to restore from a backup?

needed, then don't use a file-based database, such as Access or Paradox, but
a client/server database, instead. Access also isn't good for the Web,
because anyone who can connect to the database file via the Internet can copy
the database file, replace the database file, or just make modifications to
the database file. You probably won't like what an unauthorized developer
(i.e., hacker) might do to your database behind your back.

From your comments I'll probably keep it off of the web. I thought it might
be convenient to have acces when I'm not in the office. Its not a must though.
Do you have a reccomendation of a client/server product for comparison?

 

[Pieter Wijnen]

Comments interjected

Thank you! Do you have any Access book reccomendations? I also made other
comments below if you care to respond.



We will probably never have more than 6 (if that many) accessing the
database at the same time.

That should usually not lead to major problems. However if your records are
small & a lot of inserting takes place, be aware that Access locks 2K pages
when updating/inserting, so you may have to code to handle unexpected
locking issues. Also it is highly reccommended to split Frontend (FE - ie
Forms, Reports ec) From the Back End (BE - Data) & to give each user a copy
of the front-end.

There are a few classes taught through our IT department. I'll start
there.
I'm going to have to invest the time myself unfortunately. An estimate for
what I need from a developer as $50k+. Whatever app I decide to use I
realize
the road is going to be long. I'll start with the basics and add
functionality as I have the time.

There are several books on Access around, I haven't got any anymore as I've
givven them all away

As far as the havoc wreaking goes, is the database usually repairable or
do
I have to restore from a backup?

You have to do regular Repairs/Compacts on Access Databases to keep them
ship-shape, they tend to bloat (one main reason to split in FE/BE).
Luckily this can be done automatic (scheduled task) in newer versions.

From your comments I'll probably keep it off of the web. I thought it
might
be convenient to have acces when I'm not in the office. Its not a must
though.
Do you have a reccomendation of a client/server product for comparison?

You can make Web Pages directly in newer versions of Access to Access the
data and /or access the data through ADO. However that means two sets of
business logic as virtually all BL has to be programmed (no triggers)

HTH

Pieter

 

[Guest]

I like the Access 2003 Inside Out book from Microsoft Press I got from Barnes
& Noble.

 

[Albert D. Kallal]

That should usually not lead to major problems. However if your records
are small & a lot of inserting takes place, be aware that Access locks 2K
pages when updating/inserting, so you may have to code to handle
unexpected locking issues.

most database systems from Oracle, to sql server, to IBM's U2 system are
page based. The problem was that old versions of ms-access (say, JET in a97)
locked records on a page bases. However, for the last 3 versions of
ms-access (that goes all the way back to access 2000), record locking is now
used in JET 4, and thus this is not a problem anymore. So, yes, if you are
using a old versions (4 versions old!) away from current of ms-access, then
you did have page locking problems. However, it has been a VERY long time
since ms-access did not support record locking as opposed to page locking
for updates...