what you are looking for are "references"
In your MS Access application goto a code module if one exists if not create a new one but don't save when you are done.
With the code NOT in break mode, (i.e. not running) press F2 in the code window . then right click on the window and you will see an option for "References" if there are libraries missing they will appear at the top of the list check off and starting with "MISSING Crystal Reports bla bla bla library"
Once you've identified the files needed you can then copy them to the corresponding location on the other computers as needed.
I find that suggestion from crystal is odd. DAO360.dll is a Data Access Object library commonly used in Access 97 and in newer versions of access for backwards compatibility. There is nothing pertinent to crystal reports in that library.
"Snoop" tools may offer further insight as to which libraries are missing on those machines.
In my humble (and experienced) opinion, Crystal Reports is a buggy and confusing product that has never scaled properly as an enterprise application. You will save yourself untold hours of frustration if you dump it and use MS Access' reporting instead. Access, with VB code in the background if necessary, will do just about everything crystal will do with one tenth the headache.
Hey, let the report writers worry about it until they wise up. The weird thing about Crystal is how many people think they are experts at it, but then you look at their methods and they come up with the screwiest report plans. I don't consider myself a Crystal expert, but I've yet to meet a Crystal user whose reports I couldn't greatly simplify in 15 minutes. I never fail to find unnecessary subreports, poor query design, and usually a mess of individual rpt files that are all one-offs from eachother.
Unfortunately, I have to tell you that your bottle of wine solution may have worked on older version of Crystal distributed on floppy disks, but the new versions on CD are impervious to soaking. You will need something much more acidic.