Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / November 2006

Tip: Looking for answers? Try searching our database.

11-27-06 Concatenating rows into a diffrent table row

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Chris Lewis - 27 Nov 2006 23:53 GMT
Access Help

My job: I have a task to organize drawings and keep out duplicates.

Problem: I am working with drawings that have multiple tracking numbers that
have repetitive information among the tracking numbers. These tracking
numbers are made of a series of pieces of the drawing to make a DWG#, Line#
and Flowchart#.

Example drawing:
    DWG#: B123456-HPDK30001
    LINE#:               4HPDK -  001-1
    FLOWCHART:   HPDKMO30-1
           Parts of the drawing:   
Group#    Section    Code    Amount    other    …    Page#    Sheet
B123456    4    HPDK    30    MO30        001    1
…                           
…                           

Continue Problem: My table looks like the one above with everything in
parts. I did it this way to save time by only typing the info in once per
row. Each part can have the same info as the part above, but when the parts
become line#, they have there own unique # from the line# above. I don’t know
how to stop duplicate rows when all the parts can have similar info.

           Example similar rows:
Section    Code    Page#    Sheet
4    HPDK    001    1
5    HPDK    001    1
4    HPSR    001    1

What I have been trying to do is concatenate the 4 rows above into a linked
relationship table called Line#. When this table sees duplicates it alerts
the other table and makes you change the row as if a column was indexed (no
Duplicates). I just haven’t got this concept to work yet.

Please let me know if you have better ways of doing this same problem.
TonyT - 28 Nov 2006 17:56 GMT
Hi Chris,

You could acheive this by making the combination of each field your primary
key (ie. section/Code & Page) or you could just put code in the before update
event to check to do a dlookup to see if the data already exists.

The best approach would almost certainly be to split the common data out
into separate tables, and then use form event codes to populate the fields
with the same data as the preceeding line.

TonyT..

> Access Help
>
[quoted text clipped - 33 lines]
>
> Please let me know if you have better ways of doing this same problem.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.