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 / General 2 / April 2008

Tip: Looking for answers? Try searching our database.

combining multiple field values into 1 list string

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ruthie - 22 Apr 2008 18:36 GMT
Hi, I received data that has i record for each specialization (and there are
100 specializations) -- so if 1 individual has all the specialties, I will
get 100 records (the individual info is all the same except for that 1
specialization field)

I was able to get a unique individual record with 100 specialization fields.
How do I then turn around and combine those 100 specialization fields into 1
list string --maybe delimited by commas?

Do you have a suggestion on how to treat these records?

Thanks for any help/suggestions/work-around.

Signature

cmw

John Vinson - 22 Apr 2008 19:43 GMT
> Hi, I received data that has i record for each specialization (and there are
> 100 specializations) -- so if 1 individual has all the specialties, I will
[quoted text clipped - 6 lines]
>
> Do you have a suggestion on how to treat these records?

You need a little easy VBA code to do this. For sample code see

http://www.mvps.org/access/modules/mdl0004.htm

Signature

                 John W. Vinson[MVP]

KARL DEWEY - 22 Apr 2008 20:45 GMT
You are defeating the purpose of a relational database.  
You should have three tables -
Individual -
IndivID - autonumber - primary key
DOB - datetime
addr - text
phone - text
etc

Speciality --
SpecID - Autonumber - primary key
Title - text

Specialization --
IndivSpecID - Autonumber - primary key
SpecID- number - long integer - foreign key - related to Speciality table
IndivID - number - long integer - foreign key - related to Individual table
AssignDate - datetime
RescindDate - datetime
Remarks - memo

Speciality table will be related to Specialization in a one-to-many.
Individual table will be related to Specialization in a one-to-many.

Signature

KARL DEWEY
Build a little - Test a little

> Hi, I received data that has i record for each specialization (and there are
> 100 specializations) -- so if 1 individual has all the specialties, I will
[quoted text clipped - 8 lines]
>
> Thanks for any help/suggestions/work-around.
Ruthie - 22 Apr 2008 21:58 GMT
thanks and  I have that -- I created the following tables - Customer,
Specialties, Validation --
Signature

cmw

> You are defeating the purpose of a relational database.  
> You should have three tables -
[quoted text clipped - 32 lines]
> >
> > Thanks for any help/suggestions/work-around.
 
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.