Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Find Record Problems 1

Status
Not open for further replies.

learnasugo

Programmer
May 10, 2004
38
US
I am having problems with one of my find record command buttons. It only sees the first record, if I put in another job number for it to find it says that that record cannot be found. This is the only form that I am having that problem with, this is also the only form that has all of the tables in the form. Could this have something to do with the way that my tables are set up or my relationships? I have tried everything that I can think of and am still having this problem. Can anyone help me?

learnasugo
 
Perhaps your form is set to data entry = yes

Check that on the Form Properties Data Entry = No

If the form is in Data Entry mode, the find record function will not work

I haven't failed, I have just found 10,000 ways that it won't work!
 
I found that problem already and fixed it. I wish it could be something that simple. Can you think of another reason why it would be in such a manner?

learnasugo
 
The only other reason I can think of is that your query is not retriving the records you need.

I haven't failed, I have just found 10,000 ways that it won't work!
 
There are 6 tables in this db. Three of them I have no problem with, the other three will not let me create queries using these three tables. I have no idea why, they have basically the same type of relationship as the tables that work.

Tables that Work Tables that don't work

CSR1 Programmer1
CSR1 - PK Programmer1ID - PK
JobNumb Name
ClientID Data
Client RecvdDate
Campaign RecvdTime
Split Date
Mail CSR1ID - FK to CSR1
Submit
Merge

CSR2 Programmer2
CSR2ID - PK Programmer2ID - PK
R1WhitesApp R1WhitesDone
R2WhitesApp R2WhitesDone
R3WhitesApp R3WhitesDone
R4WhitesApp R4WhitesDone
Reason1WApp CSR1ID - FK to CSR1
Reason2WApp
Reason3WApp
Reason4WApp
CSRID - FK to CSR1

CSR3 Programmer3
CSR3ID - PK Programmer3ID
R1LivesApp R1LivesDone
R1ReasonLApp R2LivesDone
R2LivesApp R3LivesDone
R2ReasonLApp Setups
R3LivesApp Complete
R3ReasonApp CSR1ID - FK to CSR1
Released
CSR1ID - FK to CSR1

Does that help you any in understanding my tables?
 
Hmm, interesting. My first thought is that your data structure does not look normalized. It is usually a clue when you have fields that need to be suffixed with a number eg reason1, reason2, reason3 etc.

You might want to try normalizing your table structure which will make the queries more intuitive.

From what I can see, you have a separate table for each Programmer? Is this the case? If you add a 4th Programmer, do you need to add a new table?

I haven't failed, I have just found 10,000 ways that it won't work!
 
The reason that the fields are suffixed with a number is that is because sometimes we have to submit a copy of the letter that the client wants on white paper several times before it looks like the client wants. The same procedure goes for when we put it on lives (the paper that the letter will be printed on when it mails). The three tables for the CSR's and the three tables for the programmer's are how many steps they have to do to go through the process.

Does that make it any clearer?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top