Re: Checking a table for an existing entry and insert into a form?

I answered your initial post without realizing that there was already
a long thread behind it.

What ever "Complaints is, it most likely isn't a "master" table. If
it is to record an actual complaint then it's probably a child table
or a junction table.

What it tblTimes all about?

What are Accounts, Principals? What are Assignments, Hearings and
Rep(s) List?

There needs to be more explanation.

HTH
--
-Larry-
--

"Crimsonsplat" <Crimsonsplat@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:F67EB45A-0A05-4CB0-A72E-2ECEEC195042@xxxxxxxxxxxxxxxx
> Sure! Here are the tables and relationships:
>
> Complaints (The "master" table)
> Principals (one to many to Complaint)
> Type List (one to many to Complaint)
> Times (one to many to Complaint)
> Assigments (many to one to Complaint)
> Hearings (one to one to Complaint)
> Accounts (one to many to Complaint)
> Rep List (one to many to Assignments)
>
> Due to legacy issues, preferred entry pattern will be to start with
the
> Account Table, _then_ create the Complaint, select and enter a Type
(from
> combo box?), and follow up with an Assignment (from combo box?).
All the
> other tables will be used at later points during the process.
>
> Currently, there are no one-on-one form to table relationships; I
was
> complicating my life by trying to follow a legacy app which would
require all
> the tables above to connect to a single form (which meant an unbound
form an
> fields). Preferably VERY indirectly, through select & action
queries and/or
> temporary storage tables. It would really break my heart to have to
> streamline all this by going to one table, one form....Not!
>
> I can eliminate actual duplicates by hand before converting the
existing
> database; it's a pain but doable (already done in my testbed) so all
I need
> to do is prevent new dupes from arising and complete entries for the
user if
> the data is already there. (Even if the "entry" doesn't acutally
enter
> anything except a reference to the existing record).
>
> "mscertified" wrote:
>
> > It would help if you told us what these 5 tables are and what the
> > inter-relationships are between them. Normally (in a good design),
one form
> > updates one table. If you really need to update more than one
table, I'd do
> > it in the after update event for the form. Don't use macros! Use
event
> > procedures instead.
> > Regarding the duplicate records, you need an additional column for
the key
> > which will result in a compund key that is unique. Look at your
table design
> > again.
> >
> > Dorian
> >
> > "Crimsonsplat" wrote:
> >
> > > Two related questions for a complaints tracking database in
Access2000:
> > >
> > > First, the super-basic one: what is the best way to go about
taking data
> > > from a form and putting it in a table. Due to the complexity of
the business
> > > relationship, about 5 tables will need entries for each
complaint, plus
> > > standard codes will need to be looked up from about three more.
(I figure
> > > combo boxes for those, of course). I've read through many
articles and
> > > questions--more confused than ever now!
> > >
> > > Second, the headache: 95% of the records will be unique, but
about 5% will
> > > duplicate prior records in two of the tables. I've been trying
to create a
> > > macro that will fire on the LoseFocus event, and auto-insert
data from the
> > > table's fields into the form if a duplicate record exists, but I
get various
> > > errors depending on the contents of the macro's SetValue
arguments. If I'm
> > > on the right track, I'll post the full macro and error messages
for further
> > > assistance; if not, point me elsewhere.


.

Relevant Pages

  • Re: U.S. Navy 20th Century Historical Database
    ... His complaint was unclear. ... :>about the fact that a link on nwc was bad (not a link from nhc to nwc ... While I am indeed your master, you being but a lowly Marine and all, ...
    (sci.military.naval)
  • Re: Shape naming on drop
    ... Open the Drawing Explorer. ... Scroll down to the Masters section. ... Right click on every master and select Delete. ... If you don't get the complaint, then the master was not in use. ...
    (microsoft.public.visio.developer)
Loading