Forum Discussion
Append query
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.
How do I do this? How do I use a text field to store the file path?
I already have folders set up with jpgs' of the receipts. I don't know how to set up paths to them.
What data type do I use for the file paths?
Also, how do I upload files to you?
Please dont get disgusted or impatient with me. I am trying to learn.
Thanks.
- Thank you again. For some reason, I have not found the Upload key to use in this forum. Please help.
- Thank you so much for your help and consideration. There is quite a bit of material on Georg's post so it will take me awhile to work through. Hope you don't mind if I have more questions.
Hi George
Thanks for stepping in. I hope the OP finds that helpful.
@faxylady
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.
Good luck
PMFJI:
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.
