The type of the source is 1D array of double [64-bit real (~15 digit precision)]. The type of the sink is double [64-bit real (~15 digit preci

[JayWW]

I loading the same project on a different LabVIEW machine and seeing the error "The type of the source is 1D array of
double [64-bit real (~15 digit precision)].
The type of the sink is double [64-bit real (~15 digit precision)]."

This is not an issue on the other LabVIEW machine. Both are running LabVIEW 2017 SP1.

Please see the attached image.

[Jay14159265]

looks like the input is not expecting an array just a single float. 

[altenbach]

Instead of showing is your entire desktop with a disorganized truncated diagram with hidden wires, attach the actual VI to do us all a favor. Thanks.

What kid of report are you generating (HTML, Word, Excel)? (not visible in the image!). Do all machines have the same version of office installed? Same version of the report generation toolkit? 

What is the exact name of the function rejecting/accepting the broken wire? Append table to report requires a scalar for the column width, so it might be more interesting to see the code where the wire is NOT broken.

[JayWW]

---

@altenbach wrote:

Instead of showing is your entire desktop with a disorganized truncated diagram with hidden wires, attach the actual VI to do us all a favor. Thanks.

What kid of report are you generating (HTML, Word, Excel)? (not visible in the image!). Do all machines have the same version of office installed? Same version of the report generation toolkit? 

What is the exact name of the function rejecting/accepting the broken wire? Append table to report requires a scalar for the column width, so it might be more interesting to see the code where the wire is NOT broken.

---

It generates a HTML report. Same version of Office is installed on both machines and the same version of Report Generation Toolkit. 

[altenbach]

As mentioned, "append table to report" requires a scalar for the column width so we expect the code to be broken if you wire an array. If it is NOT broken on some computers, we need to find out why, but we don't have sufficient information. We cannot really tell with 100% certainty where the wire actually connects by looking at a messy code picture.

As a first step, attach your VI.

[JayWW]

---

@altenbach wrote:

As mentioned, "append table to report" requires a scalar for the column width so we expect the code to be broken if you wire an array. If it is NOT broken on some computers, we need to find out why, but we don't have sufficient information. We cannot really tell with 100% certainty where the wire actually connects by looking at a messy code picture.

As a first step, attach your VI.

---

Attached are the VIs that are encountering the same issue.

[GerdW]

Hi Jay,

there's a missing "tables" subVI in your attached VIs.

It should be located in vi.lib/Utility/NIReport.llb/Win, but it isn't on my LV2021 installation. Other RGT functions load fine for me…

In "print pl" you use AppendTableToReport instead of the missing "tables" subVI, and so it offers a different ConnPane!

[JayWW]

---

@GerdW wrote:

Hi Jay,

there's a missing "tables" subVI in your attached VIs.

It should be located in vi.lib/Utility/NIReport.llb/Win, but it isn't on my LV2021 installation. Other RGT functions load fine for me…

In "print pl" you use AppendTableToReport instead of the missing "tables" subVI, and so it offers a different ConnPane!

---

Hi Gerd,

   I've attached the tables.vi file. Thanks!

[LLindenbauer]

This sounds like someone might have been editing inside vi.lib

If you edit the system subVIs, your LabVIEW installation becomes incompatible with other installations and this kind of error can occur. You can check by comparing against a third, fresh installation of LabVIEW (on a third system, if you are concerned with recovering the edits to the system library, as they may be lost otherwise) or by comparing the offending subVIs on both installations.