Redundancy Issue

Feb 20, 2008

I’ll apologize up front; I’m not quite sure where to put this. It is an issue I’m having with a form, but it involves SQL and VBA…

I need some help with an access 2007 project I’ve been working on. I’m new to access, SQL and VBA so I’m not really sure how to make it work correctly. Here is the issue:

The form “frmAddCitationsToDissertations” does not work the way it needs to. It currently allows identical records to be made in the tblCitations. This is not correct, what I need it to do is before creating a new record look at the values from the 3 drop down records and see if that value set already exist, if it does then it should enter the existing CitationID and DissertationID in the join table. If it does not exist, then it should create a record in the tblCitations and insert the new CitationID along with the dissertationID into the join table.

The logic goes as follows:

A dissertation can have N citations.

A citation may be sited N times by any single dissertation.

Two citations may have any two of the 3 attributes in common and not be the same record, but if it has all 3 attributes in common then it is the same citation and a new record should not be created in the tblCitations, it should only be created in the join table. Two of the 3 attributes are able to be blank or null, so if a citation is simply “The bible” and the other 2 attributes are the same then I need to be able to compare it as well, and ascertain that it is the same citation.

I’m hoping for a programmatic solution, I don’t want some long involved process with forms because this database will end up having more than 50,000 citations. A long process will increase the expense of data entry exponentially.

Any advice that someone can offer is greatly appreciated. If you’re interested in helping an old dog learn new tricks you can download the database I’m working on here: http://c-helm.com/access/

View Replies


ADVERTISEMENT

Can I Eliminate This Redundancy?!

Sep 13, 2007

Hello guys & gals on here.

I've been struggeling with this problem for a couple of days now and finally decided to post here and kindly ask for assistance. I've got a pretty strong OO background, but haven't worked with databases much...

I'm trying to set up a small client database for my company. The client companies have staff members (StaffClients). Client staff can attend Events and work on Projects, which I've managed via junction tables. Our own Staff can also attend Events and work on Projects.

I've uploaded my first draft of tables and relationships here:
http://img514.imageshack.us/img514/3937/snapjl9.jpg
(sorry for the blurred bits)

Now I think I've done a fairly good job in normalising the tables, but one thing that I keep stumbling across is that I need two almost identical tables: one for our Staff and one for StaffClients.

They are subtly different, e.g. StaffClients have some extra attributes, such as JobTitle, Department and one StaffClient can be the assistant of another StaffClient (also done via a junction table). The other difference is that client staff can have different roles in a project (MainContact or Assistant) compared to our own staff (Manager or TeamMember).

As a result of these differences I have set up separate junction tables for both Staff and StaffClients, but are obviously very similar.

My question is: Is that structure sound? Or can I simplify it somehow before setting up the forms for the data entry?

Your input is kindly appreciated!!

View 9 Replies View Related

General :: Database Redundancy And Validation

Aug 16, 2013

I've inherited a database with multiple users, massive redundancies, and strict policy limitations:

1. The existing table structures must remain, despite redundancies that create problems constantly, because of multiple client programs.
2. Data entry must not be programmatic: no data can be generated by code.

I can, however,
A. Create new, interdependent tables, or
B. Validate data with criteria or VBA.

I have two rules I'd like to enforce:

Rule 1: This one is easy. Certain redundant Locations must be identical. So, all the Locations in Table A must appear in Table B as well (although B may contain Locations not in A). No Big Deal.

Rule 2: An absolute rule for every Location is that each must occur between the boundaries established for that particular Track and Section.

So, given that I have a Table with Records of Track, Section, StartLocation, EndLocation (which defines the limits for Location values)...
Track 1, Section 1: Starts at Location -100, Ends at Location 100
Track 1, Section 2: Starts at Location 50, Ends at Location 20
Track 2, Section 3: Starts at Location 0, Ends at Location 400

I want to prevent users from entering illegal locations in another Table with Track, Section, Location, like:Track 1, Section 1, Location 101 (this location is beyond the end of Track 1 Section 1)I could code this in VBA, but the downside is it won't be enforced if the user has Macros turned off by default.

View 7 Replies View Related

Cannot Copy: Data Error (Cyclic Redundancy Check)

Mar 23, 2006

Hello,

I have written an extensive Access DB Application for my company and have placed it on a cd for distribution. When we try to copy it from the CD to a folder on another machine the above mentioned error comes up. Any Suggestions. Jeff

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved