Form pre-filling too many fields.

Y

Yeahyeahyeah

I have a form that I use for managing follow-up info for job site incidents.
The form basically pulls data from 2 primary tables, Table_1 which holds the
initial incident data (I know that name is not good, but I didn't create the
database unfortunately) and tblUIRFuData2 which holds the follow-up info for
each incident. Since there are usually several followups for each incident
the tables are in a one-to-many relationship linked by a field called "AIN"
(for Arc Incident Number).

The form I use is populated by a drop down that selects the intended AIN.
Everything works fine as long as the incident has not had any previous
follow-up. The drop causes the form to fill in the required fields from
Table_1 while all the follow-up fields from tblUIRFuData2 are blank. I fill
those field in, print the report and all is well.

However, when I go select from the drop down and there has been a previous
follow-up, not only are the fields from the initial incident filled in (from
Table_1), the follow-up fields from the previous follow-up (from
tblUIRFuData2) are also filled in with detail from the first follow-up. I
need the follow up fields to be blank and can't figure out what's up.

Here's the data configuration from the forms data control panel:
Record Source: qryUIRFollowUpData
Filter: blank
Order by: blank
Allow Filters :Yes
Allow Edits: Yes
Allow Deletions: No
Allow Additions: Yes
Data Entry: No

When I change Data Entry to 'Yes' it leaves all fields blank (and I need the
fields from Table_1 filled in).

Just in case it might help, here's the code from the underlying query:

SELECT Table1.AIN, Table1.Program, Table1.ProgStreet, Table1.ProgCitySt,
Table1.ProgZip, Table1.[Consumer First Name], Table1.[Consumer Last Name],
Table1.[Incident Date], Table1.[UIR Status], Table1.IncidentDescription,
tblDDDIncidentCodes.[Incident Grade], tblUIRFuData2.chkNewInfo,
tblUIRFuData2.chkInvComp, tblUIRFuData2.chkCommDec, tblUIRFuData2.chkOAR,
tblUIRFuData2.chk30Day, tblUIRFuData2.chk3Mon, tblUIRFuData2.chk5Mon,
tblUIRFuData2.chk7Mon, tblUIRFuData2.chk9Mon, tblUIRFuData2.chk11Mon,
tblUIRFuData2.chkOET, tblUIRFuData2.chkOtherReason, tblUIRFuData2.optUpgrade,
tblUIRFuData2.optCurrStatus, tblUIRFuData2.cboPros,
tblUIRFuData2.cboIntComm1, tblUIRFuData2.txtIntComm1,
tblUIRFuData2.cboIntComm2, tblUIRFuData2.txtIntComm2, tblUIRFuData2.cboDOH,
tblUIRFuData2.cboHSPol, tblUIRFuData2.cboDCA, tblUIRFuData2.cboMedEx,
tblUIRFuData2.cboDYFS, tblUIRFuData2.cboPubAdv, tblUIRFuData2.optClosedConcl,
tblUIRFuData2.chkChgTP, tblUIRFuData2.chkTrng, tblUIRFuData2.chkPersonnel,
tblUIRFuData2.chkReassign, tblUIRFuData2.chkSusp, tblUIRFuData2.chkRemoval,
tblUIRFuData2.chkOtrAct, tblUIRFuData2.chkNoAct, tblUIRFuData2.chkPolicyChg,
tblUIRFuData2.chkChgFac, tblUIRFuData2.chkRefEmpRel, tblUIRFuData2.chkPerOtr,
tblUIRFuData2.mmoCurIncSumm, tblUIRFuData2.mmoNewInfo,
tblUIRFuData2.mmoOtrReason, tblUIRFuData2.mmoUpgrade,
tblUIRFuData2.mmoSummInvConcl, tblUIRFuData2.mmoActTaken,
tblUIRFuData2.mmoOtrRemarks, tblUIRFuData2.txtFuCompBy,
tblUIRFuData2.dtFuDate, Table1.[HAMM # / Incident #], Table1.AddComments,
Table1.[DDD Code]
FROM (tblDDDIncidentCodes INNER JOIN Table1 ON tblDDDIncidentCodes.[DDD
Code] = Table1.[DDD Code]) LEFT JOIN tblUIRFuData2 ON Table1.AIN =
tblUIRFuData2.AIN
WHERE (((Table1.[UIR Status])="pending" Or (Table1.[UIR Status])="pending
via sru"));


Any help on solving this would b greatly appreciated.

Many thanks
David
 
K

Klatuu

What you are experiencing is normal behaviour. You may try excluding
previous follow up records by using a date field in your follow up table,
then filter them by that date compared to the current date.

Yeahyeahyeah said:
I have a form that I use for managing follow-up info for job site incidents.
The form basically pulls data from 2 primary tables, Table_1 which holds the
initial incident data (I know that name is not good, but I didn't create the
database unfortunately) and tblUIRFuData2 which holds the follow-up info for
each incident. Since there are usually several followups for each incident
the tables are in a one-to-many relationship linked by a field called "AIN"
(for Arc Incident Number).

The form I use is populated by a drop down that selects the intended AIN.
Everything works fine as long as the incident has not had any previous
follow-up. The drop causes the form to fill in the required fields from
Table_1 while all the follow-up fields from tblUIRFuData2 are blank. I fill
those field in, print the report and all is well.

However, when I go select from the drop down and there has been a previous
follow-up, not only are the fields from the initial incident filled in (from
Table_1), the follow-up fields from the previous follow-up (from
tblUIRFuData2) are also filled in with detail from the first follow-up. I
need the follow up fields to be blank and can't figure out what's up.

Here's the data configuration from the forms data control panel:
Record Source: qryUIRFollowUpData
Filter: blank
Order by: blank
Allow Filters :Yes
Allow Edits: Yes
Allow Deletions: No
Allow Additions: Yes
Data Entry: No

When I change Data Entry to 'Yes' it leaves all fields blank (and I need the
fields from Table_1 filled in).

Just in case it might help, here's the code from the underlying query:

SELECT Table1.AIN, Table1.Program, Table1.ProgStreet, Table1.ProgCitySt,
Table1.ProgZip, Table1.[Consumer First Name], Table1.[Consumer Last Name],
Table1.[Incident Date], Table1.[UIR Status], Table1.IncidentDescription,
tblDDDIncidentCodes.[Incident Grade], tblUIRFuData2.chkNewInfo,
tblUIRFuData2.chkInvComp, tblUIRFuData2.chkCommDec, tblUIRFuData2.chkOAR,
tblUIRFuData2.chk30Day, tblUIRFuData2.chk3Mon, tblUIRFuData2.chk5Mon,
tblUIRFuData2.chk7Mon, tblUIRFuData2.chk9Mon, tblUIRFuData2.chk11Mon,
tblUIRFuData2.chkOET, tblUIRFuData2.chkOtherReason, tblUIRFuData2.optUpgrade,
tblUIRFuData2.optCurrStatus, tblUIRFuData2.cboPros,
tblUIRFuData2.cboIntComm1, tblUIRFuData2.txtIntComm1,
tblUIRFuData2.cboIntComm2, tblUIRFuData2.txtIntComm2, tblUIRFuData2.cboDOH,
tblUIRFuData2.cboHSPol, tblUIRFuData2.cboDCA, tblUIRFuData2.cboMedEx,
tblUIRFuData2.cboDYFS, tblUIRFuData2.cboPubAdv, tblUIRFuData2.optClosedConcl,
tblUIRFuData2.chkChgTP, tblUIRFuData2.chkTrng, tblUIRFuData2.chkPersonnel,
tblUIRFuData2.chkReassign, tblUIRFuData2.chkSusp, tblUIRFuData2.chkRemoval,
tblUIRFuData2.chkOtrAct, tblUIRFuData2.chkNoAct, tblUIRFuData2.chkPolicyChg,
tblUIRFuData2.chkChgFac, tblUIRFuData2.chkRefEmpRel, tblUIRFuData2.chkPerOtr,
tblUIRFuData2.mmoCurIncSumm, tblUIRFuData2.mmoNewInfo,
tblUIRFuData2.mmoOtrReason, tblUIRFuData2.mmoUpgrade,
tblUIRFuData2.mmoSummInvConcl, tblUIRFuData2.mmoActTaken,
tblUIRFuData2.mmoOtrRemarks, tblUIRFuData2.txtFuCompBy,
tblUIRFuData2.dtFuDate, Table1.[HAMM # / Incident #], Table1.AddComments,
Table1.[DDD Code]
FROM (tblDDDIncidentCodes INNER JOIN Table1 ON tblDDDIncidentCodes.[DDD
Code] = Table1.[DDD Code]) LEFT JOIN tblUIRFuData2 ON Table1.AIN =
tblUIRFuData2.AIN
WHERE (((Table1.[UIR Status])="pending" Or (Table1.[UIR Status])="pending
via sru"));


Any help on solving this would b greatly appreciated.

Many thanks
David
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

MS Access Form update 0
Help needed passing data from the form to a table. 0
Copy and paste in tables 1
MS365 WORD: How to Create Macro Button to CLEAR ALL fields in fill-in form 1
Publisher is filling blank lines with data 2
so not allow save if certain field sets are not unique 0
Referencing Subform from Another Form 9
Password Form 0

Top