Also, is it possible to compile the db so that people without access can
use
it? I'm thinking about using the web pages access can generate, but I don't
know anything about them...
if you're using Access 2003, you need Visual Studio Tools for Office 2003
(which includes the Access 2003 Developer Extensions) in order to create an
Access 2003 runtime application that can be used by people who don't have
the Access software. for older versions of Access, you also need additional
software, but i've no details to offer.
Does anyone know about a tutorial on how to make the front-end look better
when creating a db?
AFAIK, there's nothing specifically about building forms to *look better*,
usually in books and on websites the emphasis is on improving functionality
and ease-of-use for the user.
and "better looking" is in the eye of the beholder (or user, in this case).
what may look better to you and i (who like to do cool things <g>), or
better to a manager, who sees a form for 2 minutes when you demonstrate the
db, and what will look appealing to a user who has to stare at the form for
sometimes very long periods of time, and do his/her work quickly and
efficiently with as little eye strain as possible - may be two very
different things.
i've found that, in general, hard bright colors, fancy type or shadows or
controls outlined in color, and a crowded "busy" window, can all contribute
to eye-strain and make it unpleasant and even difficult for the user to look
at and use a form for extended periods. though i love color and love to make
things "pretty" (or impressive <g>), i've learned to keep the eye-catching
formatting confined mostly to introductory or "main menu" windows. for data
entry/display forms, in SingleForm and ContinuousForm view which can have a
lot of "background" showing, i generally stick with the default gray. while
boring, it is easy on the eyes, and doesn't distract attention from the
data. i use color sparingly, judiciously, and usually in a standardized
"code" in all the forms in the database. for instance, Red (198, not 255)
may be used on all Quit buttons; Green on all Save buttons or Continue
buttons; Dark Blue, bold for all data entry control labels; Black, bold for
all "read only" data. this can have a subliminal effect in helping users
quickly grasp the context of what they're seeing, and subtly drawing their
attention where you want it to go.
the above is all based on my own development experiences, and data entry
experiences, too - i've spent considerable time on "that side of the fence",
as well. you'll no doubt get differing opinions from others.
hth
