 lmd2
		
			lmd2
		
		
		
		
		
		
		
		
	
			09-22-2009 04:14 PM
the program generates a MS Word report using NI_report.lvclass VIs
in code this is working fine but I built and exe and it doesn't do anything when I press the button. (actually the finger changes to an hourglass for a split second)
on the Source Files pane of the build spec, in the "Always Include" panel I have
_Excel Dynamic VIs.vi and _Word Dynamic VIs.vi
is there something else I must include?
thanx
lmd2
Solved! Go to Solution.
 Mark_Yedinak
		
			Mark_Yedinak
		
		
		 
		
		
		
		
		
	
			09-22-2009 04:16 PM
09-22-2009 04:41 PM
 Matthew_Kelton
		
			Matthew_Kelton
		
		
		
		
		
		
		
		
	
			09-22-2009 05:30 PM
Are you using error handling when you call the code to generate the Word Document? If so, are you getting any specific error? Is the EXE running on the same system as the source? If not, is the version of Word for development the same as on the EXE machine?
09-22-2009 05:52 PM
there was error handling but some newer subVIs were not in the loop, just corrected that. same machine same version of office, will update this post when I run the new exe
09-22-2009 06:19 PM
ok getting error 7 occurred at Get LV Class Default Value.vi
looks like I'm missing some input
thanx everyone
should be able to find this (I hope)
09-22-2009 06:42 PM
hope someone is still out there
I inherited this project which was originally written in LV 7.1 and has been updated to 8.6.1
in the project I see that some report VIs (Initialize Word Report.vi, Write Image to Word Report.vi, etc.) are flagged missing or moved
looking at the new report VIs (class) these have changed (yet this works in code)
so now the question is how to repair or re-link or something ...
help will be greatly appreciated
thanx
lmd2
 Darren
		
			Darren
		
		
		
		
		
		
		
		
	
			09-23-2009 10:25 AM
Initialize Word Report.vi and Write Image to Word Report.vi are not part of the Report Generation toolkit. It sounds like you had some custom VIs in LabVIEW 7.1 that you'll need to find and move over to 8.6.1.
09-23-2009 10:41 AM
well I think the present code doesn't need these VIs at all, rather the issue (I think) is that they were never removed from the project (now that native toolkit VIs are used)
and it seems that though the code doesn't use or need them, just having them listed in the project (although missing) is causing the EXE to not work
does that make sense?
 Darren
		
			Darren
		
		
		
		
		
		
		
		
	
			09-23-2009 11:00 AM