Greg,
I haven't molested any of the sub reports in the Job Traveler but I did
molest the (Vantage made) sub report in the sales order pick list for
the warehouse locations. I changed them from Inventory to WIP locations
(we ship 99% from Job). This has always worked well inside or out of
Vantage. While I won't pretend to know why in your particular case you
are getting the error you are, perhaps looking at my report may help
you. Let me know if you want a copy of it.
Rob Bucek
Manufacturing Engineer
PH: 715-284-5376 ext 311
FAX: 715-284-4084
<http://www.dsmfg.com/>
(Click the logo to view our site)
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of pilotgl
Sent: Friday, May 08, 2009 2:00 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Production Floor Traveler
I have a crystal reports/Vantage question on the production floor
traveler. I have rebuilt the sub report RawMaterialComponents to display
the BOM material based upon the operation number that is corresponding.
In the crystal environment this works great. You look at operation 40
and the operation 40 materials and barcodes show up. I have rebuilt the
links of the subreport to pull this correctly. I use my XML data
generated from Vantage and not a problem.
But I go back in and make this a report style pulling to this custom
report and I get the problem. I get a stack trace error telling me the
subreport name is not a valid name. I go to do the print preview of this
report and get this every single time. I have done everything possible
in testing to keep the same naming conventions and everything in place
with the original names. But I get this error every single time I
relocate the sub report.
Anybody have any ideas at all what else could be going on in the
background that is generating this issue? There has to be something
getting passed through a Vantage code set in the background I feel that
is giving me this stack error. Any help or suggestions on this issue
would be greatly appreciated.
Thanks,
Greg Lankston
[Non-text portions of this message have been removed]
I haven't molested any of the sub reports in the Job Traveler but I did
molest the (Vantage made) sub report in the sales order pick list for
the warehouse locations. I changed them from Inventory to WIP locations
(we ship 99% from Job). This has always worked well inside or out of
Vantage. While I won't pretend to know why in your particular case you
are getting the error you are, perhaps looking at my report may help
you. Let me know if you want a copy of it.
Rob Bucek
Manufacturing Engineer
PH: 715-284-5376 ext 311
FAX: 715-284-4084
<http://www.dsmfg.com/>
(Click the logo to view our site)
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of pilotgl
Sent: Friday, May 08, 2009 2:00 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Production Floor Traveler
I have a crystal reports/Vantage question on the production floor
traveler. I have rebuilt the sub report RawMaterialComponents to display
the BOM material based upon the operation number that is corresponding.
In the crystal environment this works great. You look at operation 40
and the operation 40 materials and barcodes show up. I have rebuilt the
links of the subreport to pull this correctly. I use my XML data
generated from Vantage and not a problem.
But I go back in and make this a report style pulling to this custom
report and I get the problem. I get a stack trace error telling me the
subreport name is not a valid name. I go to do the print preview of this
report and get this every single time. I have done everything possible
in testing to keep the same naming conventions and everything in place
with the original names. But I get this error every single time I
relocate the sub report.
Anybody have any ideas at all what else could be going on in the
background that is generating this issue? There has to be something
getting passed through a Vantage code set in the background I feel that
is giving me this stack error. Any help or suggestions on this issue
would be greatly appreciated.
Thanks,
Greg Lankston
[Non-text portions of this message have been removed]