This is just a guess...I have no experience of RAID drives.

It sounds like "happenstance" to me. Can this be proved for more than a single
installation? They may have other problems, merely by happenstance. That is
how I'd see it, if I came across it and until I proved otherwise. I don't
recall a discussion of RAID drives in this context.

Either RAID drives work reliably with all software or they dont...

It is often said that Access is particularly sensitive to things like (network
reliability, whatever). There are enough reports, to suggest Access is a good
test of a "system"!

Other than that, I wouldn't speculate. For instance, with a Runtime Access she
has no business speculating that it's to do with "runtime libraries" (Since
Access is actually identical but with different disabling registry settings).
Even if they were different libraries, what is the speculation of "runtime
libraries" vs something else? This would assume they have tested OK under full
Access, but you haven't said that they have. Also, you don't really give a
precise error description.

(I myself am struggling with some imaging extensions which works on some
installations and not others. The customer thinks it's related to Runtime
Access or not, because that's how it seems to them. But I think it's related
to Graphics Filters or OLE Imaging Servers and the like, which is not really
related to Runtime at all it just seems so, on the face of it. Irrelevant,
except how easy it is to blame something when you have insufficient
installations or in my case inexperience with a given aspect)

Chris

(does her installation otherwise work fine if she installs the files on her
local disk? Access itself should always be installed on the local disk
(excepting Terminal Server), so "runtime libraries" would (for yet another
reason) hardly be that problem)
(I'm just thinking, and I'm now out ;-) )