2. if you're using somebody else's database, hopefully a user interface as
been built for you. rule of thumb would be to use that interface rather than
to enter/edit data directly in tables. if the db doesn't come with a user
interface, see #3 below.
3. creating an Access database consists of two "parts": 1) analyzing the
process that the database must support, and writing the tables/relationships
structure (data modeling, and 2) creating those tables/relationships in
Access, and then building the queries/forms/reports to interact with the
data. for more information and recommended reading, see
http://home.att.net/~california.db/tips.html - tips #1 and #2. when you
begin actually building the database, suggest you come back to the page and
read the rest of the tips, which are geared specifically to newbie
developers.
hth
"Jim Hughes" <jh******@twmi.rr.com> wrote in message
news:9T******************@tornado.ohiordc.rr.com.. .
Good Afternoon ...
... I hope the sun is shining in your domain ...
... if you would be so kind, would you please suggest MS Access reading
material, based on the following input:
1. Knowledge level ... Newbie
2. As a user of MS Access - written programs; i.e., I will be using
someone's program; I might have to enter data, look up records, etc.
3. As a creator of MS Access programs
Thanks for your time and consideration.
Jim Hughes
********************************************
