Thank you Guessed,
Quote:
Originally Posted by Guessed
I don't usually have a problem with References unchecking themselves so I can only guess what might be happening on your machine.
|
If nothing else, it's nice to know that this issue is not evidence of yet another illiteracy on my part. I did contact Microsoft on this issue. The agent contends that the issue is because our computers are not running the most recent BIOS and that I need to contact the hardware manufacturers for the most recent upgrade. I remain skeptical and asked to escalate the issue to verify before dealing with the manufacturers. And thus risking corrupting both our PCs.
Quote:
|
Firstly, I would check that the code compiles correctly on her machine. If it works on a 32bit version of Word then you are 99% of the way there but there may be some code that fails to compile on a 64bit machine.
|
Because the first form does appear, I didn't think to compile on her machine. I'll give that a try. However, clicking on that form's control displays the msgbox message I coded (to alert of the missing "Excel 16.0 Object" reference).
Quote:
|
Secondly, verify which version of Excel she has on her machine. If it happens to be older that v16 then you should be able to reference Excel 15.0 instead.
|
My wife is on her machine right now so I'll have to check later. But her MSO 365 Office shows Word as 2016 and I don't recall seeing anything but the Excel 16.0 in the reference list.[/QUOTE]
Quote:
|
Since the file you are transferring is a template which contains building blocks there shouldn't be a reason to also copy those building blocks to her Normal.dotm template. If you have code in your template that inserts those building blocks, just make sure the VBA gets the BBs from that template.
|
No, I'm not inserting into the Quick Parts. So I'll not worry about that right now.