That meant that tho job (Word2003/VBA) was ready to be ported to the second laptop. I have a third laptop and will set up a stream of work being fed from one laptop to another, a production line of data processing. I get a job working on this machine, then memory-key the template to the second machine and start R&D on the next filter.
I had previously made Restore Points, backed up my data partition, then copied my data partition to the other two machines which, although Win7, are now a very close copy of the data partition on the main machine. In other words, anything that is visible on this main machine is available and visible on the other two machines. They are not clones, but are as close as I can make them. (They have different AutoExec.bat files for one thing!)
Of course, nothing ever works the first time, and I found that I had to hook up my UW.dot utility library AND the RegEx library, before the program would run, but then, run it did!, so a small hurdle, and I am in business on two machines; tomorrow the third machine.
Question 1 :Why was it necessary to hook up two of my references but not the first five?
Question 2 :Why was it necessary to hook up my UW.dot? It is in the same place on my data partition, "T:\Greaves\Startup\Word".
Question 3 :Why was it necessary to hook up one MSoft library(VBScript), but not the others (VBApplications, Office11, Word11)? These are, I would suppose, all in the same place on the C: drive, or have visible pointers to themselves via the registry or whatever. (I hope we don't get into early/late binding again
)Thanks for any lay-man's terms. This is not a big deal; I just couldn't come up with an idea of why two out of the seven references are broken. I may learn more tomorrow when I port to the third machine.
Cheers
Chris
