Aaron, thanks to your comment about using BAQ to publish a web page with
current labor transactions, I set one up yesterday with this same data and
my plant floor people love it. They have been unhappy since the loss of the
"who was clocked in screen" on the old data collection screen. Now they not
only see who is currently clocked in but what job/asm/op they are working
on. I do have a question about the process server. You said that it
processes all BAQs with an output file name specified in the query. Is it
just the ones with xml specified as the output format? I have many existing
queries with ASCII or Dbase as the format and it is not processing them,
only the new one I set up yesterday.
Thanks again for your input, I was actually popular yesterday for a short
time.
Jerry Boyle, Controller
Sipco Molding Technologies
Meadville, PA. 16335
p 814.724.2243 x53
f 814.724.2244
Vantage 6.10.506
-----Original Message-----
From: Aaron Hoyt [mailto:hoyt@...]
Sent: Friday, May 28, 2004 5:59 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: BAQ and ASP pages
John,
Let me caution you about a couple things.
For static data...export as XML, but do not save the path in the "Output
file name" of the query. If you choose to use the process server it will
process any BAQ with a location in that field. Also set up a delay in the
process server for the BAQ if you plan to use it. I run my process server
from the server, allowing the server to use it's awesome power to run the
queries, but it does put a draw on the server, so be careful how many and
how complex the Queries are you plan to run automatically (by entering a
path in the "Output file name" field in the query). Also, remember if you
run the process server from the server, the path you choose will be used on
the server, so if you pick c:\...
that is where it will be on the server (I use UNC for mine).
The last thing. The ASP pages that Vantage generates can be processed by an
IIS server, so you might want to set up a virtual directory on your Intranet
(assuming you have one) for the ASP, XML and such to be exported to.
Ok, so one more thing. Test, test and retest. You may want to export the
XML files to a local directory on the server running the process server and
then schedule a simple copy command to copy them over to another location
every so often. Again, something I learned was if the XML is in use as the
query runs, the process server stops and you have to reset it (kind of a
pain).
Feel free to contact me if you need additional assistance.
Good luck,
Aaron Hoyt
Hittite Microwave
current labor transactions, I set one up yesterday with this same data and
my plant floor people love it. They have been unhappy since the loss of the
"who was clocked in screen" on the old data collection screen. Now they not
only see who is currently clocked in but what job/asm/op they are working
on. I do have a question about the process server. You said that it
processes all BAQs with an output file name specified in the query. Is it
just the ones with xml specified as the output format? I have many existing
queries with ASCII or Dbase as the format and it is not processing them,
only the new one I set up yesterday.
Thanks again for your input, I was actually popular yesterday for a short
time.
Jerry Boyle, Controller
Sipco Molding Technologies
Meadville, PA. 16335
p 814.724.2243 x53
f 814.724.2244
Vantage 6.10.506
-----Original Message-----
From: Aaron Hoyt [mailto:hoyt@...]
Sent: Friday, May 28, 2004 5:59 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: BAQ and ASP pages
John,
Let me caution you about a couple things.
For static data...export as XML, but do not save the path in the "Output
file name" of the query. If you choose to use the process server it will
process any BAQ with a location in that field. Also set up a delay in the
process server for the BAQ if you plan to use it. I run my process server
from the server, allowing the server to use it's awesome power to run the
queries, but it does put a draw on the server, so be careful how many and
how complex the Queries are you plan to run automatically (by entering a
path in the "Output file name" field in the query). Also, remember if you
run the process server from the server, the path you choose will be used on
the server, so if you pick c:\...
that is where it will be on the server (I use UNC for mine).
The last thing. The ASP pages that Vantage generates can be processed by an
IIS server, so you might want to set up a virtual directory on your Intranet
(assuming you have one) for the ASP, XML and such to be exported to.
Ok, so one more thing. Test, test and retest. You may want to export the
XML files to a local directory on the server running the process server and
then schedule a simple copy command to copy them over to another location
every so often. Again, something I learned was if the XML is in use as the
query runs, the process server stops and you have to reset it (kind of a
pain).
Feel free to contact me if you need additional assistance.
Good luck,
Aaron Hoyt
Hittite Microwave