View Single Post
  #2  
Old June 5th, 2010, 09:13 PM posted to microsoft.public.access.forms
Access Developer
external usenet poster
 
Posts: 12
Default SubForm, or something Else?

IMNSHO, there is no good answer to your question except: back up, start
over, and avoid multi-value fields like the plague. Also, IMNSHO, those were
included to allow support of existing non-relational data in SharePoint and
that is the only valid use for them (except for the case when that data will
ONLY, EVER be read by humans without any further manipulation or proccessing
in Access -- a situation that is difficult for me to imagine). Finally,
penultimately IMNSHO, it does not speak well of the judgement or learning
ability (because of the plethora of advice from experienced Access
developers here and elsewhere to avoid using multi-valued fields) of an
Access user who chooses to use this feature in any other circumstance than
what I described.

--
Larry Linson, Microsoft Office Access MVP
Co-author: "Microsoft Access Small Business Solutions", published by Wiley
Access newsgroup support is alive and well in USENET
comp.databases.ms-access