Jul 08 2021 04:48 PM
Jul 08 2021 04:48 PM
I am trying to append several entries from one table to another. I keep getting the error message, "An Insert Into Query cannot contain a multi-valued field." In the criteria row I put "between 07/01/21 and 07/08/21." When I chose Append Query, I chose the correct table from the Append to Dialog Box. What am I doing wrong?
Jul 08 2021 11:54 PM
Sorry., my original reply didn't appear so the above comment made little sense.
Multivalued fields (MVFs) are in many ways a poor choice and most experienced developers will recommend avoiding their use. See my article http://www.mendipdatasystems.co.uk/multivalued-fields/4594468763.
The issue is that they depend on a deep hidden system table over which you have no control.
The error message is clear. MVFs cannot be used in INSERT (append) queries. This is the result of the deep hidden table. There is no simple work round. You will also be unable to use MVFs in make table or delete queries...though update queries can be done.
Recommend you replace all MVFs with standard fields, one value per record. You will find life becomes far easier
Jul 14 2021 03:52 PM
Jul 25 2021 12:39 PM
Jul 25 2021 02:01 PM
As already explained, attachment fields are a special type of MVF and should be avoided as well.
I never use either of those datatypes in Access and am unable to assist with making these work for you.
Instead of attachment fields, store the files outside Access and use a text field to store the file paths in Access.
Jul 25 2021 06:17 PM
Jul 26 2021 06:55 AM
As Colin has pointed out, MS in their "wisdom" introduced some "user friendly" features into Access which ultimately break down In Real Life situations because of their inherent limitations. That includes Multi-Value Fields and Lookup fields in tables. After years of experience, most Access developers learn to avoid them and also recommend others avoid them.
I know of a couple of successful Access users who do implement Mult-Value Fields, but the situations in which they use them are very narrowly defined. For example, one that I'm thinking of has a series of charts that use scales of say, 1 to 5 or 1 to 10. Having an MVF with those values makes it easy to select a value for a data point on a scaled chart, but there is NO other user of them in that application. No input and no modifications are needed or allowed, so the inherent weaknesses of MVF's don't hurt.
I have a small demo on my website which illustrates a method of creating a membership directory with pictures of members. I suggest it as a reference because it uses the method Colin suggests (external image files and links to them in a field in a table). Perhaps it can help clarify a bit.
Jul 26 2021 11:28 AM
Thanks for stepping in. I hope the OP finds that helpful.
The file paths should be stored in a Short Text field. That gives a limit of 255 characters which should be more than enough for this purpose.
I have another example which may help: Folder Image Viewer
I recommend you look at the two examples and try to adapt them for your needs.
By doing that, you will learn far more than if we just 'do it for you'
If you get stuck, upload what you have done and someone will look at it.
Jul 26 2021 06:18 PM