Originally Posted by
Bob Fitz
I would not use a multi-value field. IMHO it is better to normalize the data and save it in a table.
And FYI, that's going to be the advice you get from most experienced developers here, and elsewhere! As someone recently wrote, just because the the Boys of Redmond made it possible for you to do something, in Access, doesn't mean that you should!
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007