Duplicated data due to structure?

Tay

likes garlic
Local time
Today, 03:09
Joined
May 24, 2002
Messages
269
Hopefully someone can offer me some advice on this.

I have a db which is now being used in other offices. To do this, I just copied the structure but not the data. All versions of this db have been working fine (for months) until I changed some data today. What I'd like to know is a) what should I change to get it to work? Or b) another (better) way of achieving the same thing.

The set-up

I have a form which opens when the db opens. I have 2 listboxes on it where users can pick what they want. I figured this was better than having a load of buttons.

I have 3 tables and 2 junction tables (this is probably where my problem lies).
tblFrontEnd1 = DocumentType, DocumentID
tblFrontEnd2 = DocumentGroup, DocumentGroupID
tblFrontEnd3 = DocumentOption, ActualDocumentName, DocumentOptionID
tblJoinFrontEnd12 = DocumentID, DocumentGroupID
tblJoinFrontEnd23 = DocumentGroupID, DocumentOptionID

So, a DocumentType will be either Form, Report or Query. The DocumentGroup will be 'Contact Details' etc. The document Group can have more than one DocumentType. DocumentOption is the name I give to a document 'Contact Input Form', along with its actual name.
My problem is that when I now open the start-up form and choose say 'Contact Details' (which contains both forms and reports), is that the same document is appearing twice. Some documents will open, others won't.
I don't understand why the same thing is working on one version of the db, and not the other. The tables are identical, the queries are identical, the form is identical. I've spent all day on this so far, and completely baffled as I just can't see a difference between the two db's.
Any ideas, anyone? Please?
:confused:
 
What version of Access are you using?

If you change the data back do the listboxes work again [to prove it is data dependant]
It sounds like your joins need adjusting to re-assert uniqueness for the changed data.
 
Thank you for replying. I have managed to sort the problem - it was actually down to a query used for doing the front end form. I did this so long ago, I really have no idea why I set the form up in this way. When I get time I will have a re-think and find a better way of achieving this. 5 tables, 3 queries and a form seem a bit OTT. :rolleyes: :)
 

Users who are viewing this thread

Back
Top Bottom