Prev: have casting calls for female models in buffalo ny
Next: Models, casting calls
From: Lars Brownies on 23 May 2010 08:12
Thanks.
Lars

"Mark Andrews" <mandrews___NOSPAM___(a)rptsoftware.com> schreef in bericht
news:OqdQRea#KHA.5916(a)TK2MSFTNGP04.phx.gbl...
> That looks right. Perhaps more fields in the activity table (status of
> activity, notes etc...).
>
> The activity table is usually the table with the most records in a CRM
> system.
>
> --
> Mark Andrews
> RPT Software
> http://www.rptsoftware.com
> http://www.donationmanagementsoftware.com
>
> "Lars Brownies" <Lars(a)Browniew.com> wrote in message
> news:ht7vuq$1qgc$1(a)textnews.wanadoo.nl...
>> For monitoring recruitment actions per applicant I need to store about 50
>> actions per applicant. The activity table would look like:
>>
>> ApplicantID*
>> ActivityID*
>> DateStart
>> DateEnd
>>
>> My concerns are:
>> 1. The table would have an enormous amout of records if I had let's say
>> 30,000 applicants.
>> 2. When an new applicant would be added I would have to automatically add
>> all the 50 action records, otherwise the user would have to pick them
>> manually. Also some jobs require other applicant actions than others.
>>
>> A not normalized table would seem easier but would require a table design
>> change every time there was a new type of action, which is also not
>> desirable.
>>
>> How would you deal with such a situation?
>>
>> Thanks, Lars
>>
>>
From: KenSheridan via AccessMonster.com on 23 May 2010 11:13
Better, I'd have thought, would be a multi-select list box in which you can
select any number of activities to be assigned to an applicant simultaneously.
The list box can be limited to the activities relevant to the selected job,
but first you'd need a JobActivities table with columns JobID and ActivityID
to model the many-to-many relationship between jobs and activities. The list
box's RowSource property would then be something like:

SELECT Activities.ActivityID, Activity
FROM Activities INNER JOIN JobActivities
ON Activities.ActivityID = JobActivities.ActivityID
WHERE JobID = Form!cboJob
ORDER BY Activity;

where cboJob is a control in the form whose value is the JobID of the
selected job and Activities is a table of all Activities. The first column
of the list box would be hidden by setting its ColumnWidths property to
something like 0cm;8cmIn cboJob's AfterUpdate event procedure requery the
list box with:

Me.lstActivities.Requery

You can then put some code in a 'Confirm' button's Click event procedure to
loop through the list box's ItemsSelected collection and insert a row for
each selected activity into the table which models the relationship between
applicants and activities by executing an SQL INSERT INTO statement. What
you do about the start and end dates is for you to decide; you might want to
insert the same dates into each row at this stage, or you might want these
entered individually via a form at some later stage in the process.

You could if you wish include a 'Select All' button to assign all activities
for the selected job with code like this:

Dim n As Integer

For n = 0 To Me.lstActivities.ListCount - 1
Me.lstActivities.Selected(n) = True
Next n

Similarly, to deselect all:

Dim n As Integer

For n = 0 To Me.lstActivities.ListCount - 1
Me.lstActivities.Selected(n) = False
Next n

Ken Sheridan
Stafford, England

Lars Brownies wrote:
>> I do not see a valid reason for pre-populating the Activity Table with a
>> copy of every possible activity for each applicant, especially as you
>> state that not all applicants records will need all the activities.
>
>Thanks. I thought of it more as a checklist to save users work.
>
>> When you add an activity record for an applicant, provide a ComboBox from
>> which the user can choose the appropriate activity. A ComboBox is ideal,
>> because with the default AutoExpand option, you can begin typing and it
>> will automatically scroll the drop-down list -- you don't have to scroll
>> through all the earlier options to reach the one you want.
>
>The activities depend on the job they apply to. Maybe I can offer combo
>values depending on the job.
>
>Lars

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access/201005/1

From: Lars Brownies on 23 May 2010 14:38
Good idea! Thanks,
Lars

"KenSheridan via AccessMonster.com" <u51882(a)uwe> schreef in bericht
news:a8704b524cad3(a)uwe...
> Better, I'd have thought, would be a multi-select list box in which you
> can
> select any number of activities to be assigned to an applicant
> simultaneously.
> The list box can be limited to the activities relevant to the selected
> job,
> but first you'd need a JobActivities table with columns JobID and
> ActivityID
> to model the many-to-many relationship between jobs and activities. The
> list
> box's RowSource property would then be something like:
>
> SELECT Activities.ActivityID, Activity
> FROM Activities INNER JOIN JobActivities
> ON Activities.ActivityID = JobActivities.ActivityID
> WHERE JobID = Form!cboJob
> ORDER BY Activity;
>
> where cboJob is a control in the form whose value is the JobID of the
> selected job and Activities is a table of all Activities. The first
> column
> of the list box would be hidden by setting its ColumnWidths property to
> something like 0cm;8cmIn cboJob's AfterUpdate event procedure requery the
> list box with:
>
> Me.lstActivities.Requery
>
> You can then put some code in a 'Confirm' button's Click event procedure
> to
> loop through the list box's ItemsSelected collection and insert a row for
> each selected activity into the table which models the relationship
> between
> applicants and activities by executing an SQL INSERT INTO statement. What
> you do about the start and end dates is for you to decide; you might want
> to
> insert the same dates into each row at this stage, or you might want these
> entered individually via a form at some later stage in the process.
>
> You could if you wish include a 'Select All' button to assign all
> activities
> for the selected job with code like this:
>
> Dim n As Integer
>
> For n = 0 To Me.lstActivities.ListCount - 1
> Me.lstActivities.Selected(n) = True
> Next n
>
> Similarly, to deselect all:
>
> Dim n As Integer
>
> For n = 0 To Me.lstActivities.ListCount - 1
> Me.lstActivities.Selected(n) = False
> Next n
>
> Ken Sheridan
> Stafford, England
>
> Lars Brownies wrote:
>>> I do not see a valid reason for pre-populating the Activity Table with a
>>> copy of every possible activity for each applicant, especially as you
>>> state that not all applicants records will need all the activities.
>>
>>Thanks. I thought of it more as a checklist to save users work.
>>
>>> When you add an activity record for an applicant, provide a ComboBox
>>> from
>>> which the user can choose the appropriate activity. A ComboBox is ideal,
>>> because with the default AutoExpand option, you can begin typing and it
>>> will automatically scroll the drop-down list -- you don't have to scroll
>>> through all the earlier options to reach the one you want.
>>
>>The activities depend on the job they apply to. Maybe I can offer combo
>>values depending on the job.
>>
>>Lars
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access/201005/1
>
First  |  Prev  | 
Pages: 1 2
Prev: have casting calls for female models in buffalo ny
Next: Models, casting calls