Multivalued field join clause problems - Access 2007

[techfreek]

I am trying to import a multivalued field into my table (Used the basic
Issues set up, just where multiple people can be assigned to the same issue)
I set it up so under supporting objects, issues table has the multivalued
Assigned to field. I was trying to link it up to the issue list form so I can
view it easier by Adding existing fields, but now I am stuck in design mode
because it says "The multi-valued field 'Issues.[Assign.To]' is not valid in
the specified JOIN clause" Any ideas on how I can fix this? let me know if
you need more info or if I am in wrong forum

 

[Roger Carlson]

My advice is to not use a multi-value field for precisely this reason. They
seem like a good idea at first, but they come back to bite you when they're
really hard to get rid of. Better to not use them in the first place.

 

[techfreek]

Anyway to make so I can assign multiple people to the same "issue" because
that is pretty much the core of what I trying to make happen in this.

My advice is to not use a multi-value field for precisely this reason. They
seem like a good idea at first, but they come back to bite you when they're
really hard to get rid of. Better to not use them in the first place.

--
--Roger Carlson
MS Access MVP
www.rogersaccesslibrary.com

I am trying to import a multivalued field into my table (Used the basic
Issues set up, just where multiple people can be assigned to the same
issue)
I set it up so under supporting objects, issues table has the multivalued
Assigned to field. I was trying to link it up to the issue list form so I
can
view it easier by Adding existing fields, but now I am stuck in design
mode
because it says "The multi-valued field 'Issues.[Assign.To]' is not valid
in
the specified JOIN clause" Any ideas on how I can fix this? let me know if
you need more info or if I am in wrong forum

 

[Douglas J. Steele]

The "classic" approach (which is actually what Access does under the covers
with multi-value fields) is to introduce a third table to resolve the
many-to-many relationship.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

Anyway to make so I can assign multiple people to the same "issue" because
that is pretty much the core of what I trying to make happen in this.

My advice is to not use a multi-value field for precisely this reason.
They
seem like a good idea at first, but they come back to bite you when
they're
really hard to get rid of. Better to not use them in the first place.

I am trying to import a multivalued field into my table (Used the basic
Issues set up, just where multiple people can be assigned to the same
issue)
I set it up so under supporting objects, issues table has the
multivalued
Assigned to field. I was trying to link it up to the issue list form so
I
can
view it easier by Adding existing fields, but now I am stuck in design
mode
because it says "The multi-valued field 'Issues.[Assign.To]' is not
valid
in
the specified JOIN clause" Any ideas on how I can fix this? let me know
if
you need more info or if I am in wrong forum

 

[techfreek]

Thank you. I managed to actually figure out a work around to do what I
needed. Thanks anyways.

The "classic" approach (which is actually what Access does under the covers
with multi-value fields) is to introduce a third table to resolve the
many-to-many relationship.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

Anyway to make so I can assign multiple people to the same "issue" because
that is pretty much the core of what I trying to make happen in this.

My advice is to not use a multi-value field for precisely this reason.
They
seem like a good idea at first, but they come back to bite you when
they're
really hard to get rid of. Better to not use them in the first place.

I am trying to import a multivalued field into my table (Used the basic
Issues set up, just where multiple people can be assigned to the same
issue)
I set it up so under supporting objects, issues table has the
multivalued
Assigned to field. I was trying to link it up to the issue list form so
I
can
view it easier by Adding existing fields, but now I am stuck in design
mode
because it says "The multi-valued field 'Issues.[Assign.To]' is not
valid
in
the specified JOIN clause" Any ideas on how I can fix this? let me know
if
you need more info or if I am in wrong forum