Thank you John and Pieter,

Yes, I certainly agree with you sentiments. Thing is, I am fairly new at
ACCESS (4 months) and the feature of being able to simply attach documents
directly to a field sounded like a good idea at the time.

I must say, it served me well for a while too. While I only used simple
queries...lol

Then I became a bit more confident with ACCESS and started to build more
complex queries. That is where the fun started. I only became awareof such a
thing as multi-vulue fields when the error messages popped up...:-) After
some reading up and much frustration, I am beginning to understand why.

At first I thought it was merely a "old school purist" thing, but I now
understand that it is fundamentally not a good idea.

So, How do I search more than one table simultaneously if I cannot append?
Or alternatively, how do I save documents in a database table? This
application is for a document control system, but the same would apply if one
wants to build a simple photo album?

The child table idea does not seem to solve anything, because I will then
simply move the problem to another table if I attach documents there, or not?

Looks like stumbled upon a touchy subject here...lol

Your response are really much appreciated.

Please continue with this thread, because I am open for suggestions and
definately willing to abondon the attachment idea, but need something to
replace it with.

Cheers
Dawie Theron

"John W. Vinson" wrote:

On Mon, 01 Mar 2010 07:55:45 GMT, "PieterLinden via AccessMonster.com"
u49887@uwe wrote:

Dawie Theron wrote:
I need to append a number of tables.

I make use of an APPEND QUERY and it works fine.

BUT, for one part of my application, I need to work with tables which
contain multi value fields (Attachments).

I could not find a way around that. Please help

Dawie Theron

Why would you want to use multi-valued fields? Why not just create a child
table and do it the right way? I remember a looong time ago when the
FileMaker folks finally realized that MVAs were a bad idea... lots of fun to
sort out. I definitely wouldn't recommend using a feature like that.

You should have heard the meeting between MVP's and the Access development
team at the MVP summit a few years ago. Blistering... we almost got thrown
out, and I think some feelings were hurt on both sides, unfortunately.

I absolutely agree. Bad idea, bad misfeature, unnecessary and hard to work
around... but added because there was a requirement to interface with
SharePoint.
--

John W. Vinson [MVP]
.