ju************@gmail.com wrote:
Hello,
I've just started a new job where at interview I said my week point was
MS Access. I got the job & they've asked me to create a DB on Access
97 to log calls to the IT department & keep a record of the action
taken. I thought I was going quite well I have talbes for new call,
call details, caller, equipment, escalation routes, contact details for
escalation routes, I got all the relationships up & runing (I think) &
then did a nice form to fill in to log new calls using fields from a
number of the tables that should be filled out. Well b****r me if it
didn't work. one error i get is that I cant type stuff in due to
recordset properties (but I cant find a record set thinggie to edit) &
then when I can type stuff in one field it does two wiered things,
firsly it puts the same data in that field on every new record I create
(within the form) but that same data does not apear in the table!
Obviously I need help - can anyone give me some pointers or suggest a
good website for adivce (or does anyone know where I can download a
ready made one).
Your description suggests you did a good job of database design; you,
at least, took into consideration normalization, relationships etc.
You indicate that you have a problem with a form. Before we can help
you with that we would have to know some more about the form. Is it a
bound form, that is does the form have a recordsource; if so what is
the recordsource? If it's a saved query then we will likely need to
know the sql string of the query. Does the form default to continuous
form display, or a single record at a time? Do each of your tables have
an indexed, probably primary key, identity field?
After that we could attack one problem at a time. You could choose the
simplest, perhaps, first. I think you should not despair. It sounds to
me as if you have done some good work. It may be that one simple
misunderstanding is causing your form to misfunction and that if we can
clear that one thing up, everything may work.
I am not a fan of Access 97 being used today, not because its bad, but
because its old. But IMO Access 2000 is unlikely to be helpful in this
case. There is no reason Access 2000 will work better than Access 97,
and in fact, because of its greater complexity and extremely poor state
on initial delivery (since repaired with Service Packs 1 through 7864)
it may not work as well.