The first is focused on soundfiler; and I've seen similar questions posted but the responses to them ones don't seem to work for me.

I'd like to load up a load of samples from the getgo,

I'm using [read -resize /genepatch/kick.wav Kick(

[loadbang]
|
[read -resize /genepatch/kick.wav Kick(
|
[soundfiler]

I keep getting an error:

soundfiler_read: /Genepatch/kick.wav: No such file or directory

I've tried renaming, removing caps etc, and I've tried to write the whole path.

The whole path to the sample is quite long:

D:\Digital Music & Sound Arts\AG 1012 - Practice 3 - Creative Audio Systems\Project 2 -Generative Music\Genepatch

I've tried to put the whole path in but that doesn't work, I've removed spaces, and I've used underscores but still nothing.

The only way I can get this to work is to place the folder just in D (D:\Genepatch\kick.wav)

But this is really inconvenient. Can anyone see any user issues that I may be making with the paths in my 1st example? It's starting to get infuriating.

Secondly, I'm curious as to whether it's better to use 1 [dac~] or multiple.
I'm trying to make a generative patch using a few different synths I've made. Is it best for each synth/sampler to go to it's own dac~ or should I just use 1 dac~ for the whole patch?

Many thanks

The spaces in your path might be creating problems, try replacing them with underscores, for example D:\Digital_Music_&_Sound_Arts\AG_2012 etc.
The forward and backward slashes should also be they way they are on you path, I think, plus Pd is case sensitive, so if your directory is initialized with a capital letter, then you should use it that way (Genepatch instead of genepatch).
[soundfiler] can't know that the path you give is only a part of the real path, the object needs the whole one.
Concerning [dac~], there's no real difference whether you use one or many AFAIK. If you want your patch to be more tidy you can also use [throw~] and [catch~].