Dawie,
Maybe it's time for more details. Otherwise, I'm not sure if I'm answering
your question. Some table has a MVA field where you can add several
documents. This is essentially a one-to-many relationship sort of packed
inside your table. But Access is already relational, so why not just break
that one-to-may relationship right now and put the individual multiple values
into another table? Why would that cause a problem with your data?

What are you searching for? You can create a query joining the two tables
(primary key from parent record to foreign key to child table) and then open
that or base a read-only form on that... or use a subform...

Why do you need to save documents in your database table? Are you protecting
them from modification?

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?

Okay... please explain what you are trying to do with the data. I can't tell
why the "child table idea does not seem to solve anything". How do you
intend to use the attachments in the child table?

Pieter

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...eries/201003/1