BAQs for Job PickList & Job Traveler Reports

You might consider making a copy of the data definition for the Pick List
and Job Travelers and adding tables to it that you need. I've been
successful in doing this in the past and in most cases it worked.



Dale



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
amvarghai
Sent: Thursday, July 21, 2011 12:09 PM
To: vantage@yahoogroups.com
Subject: [Vantage] BAQs for Job PickList & Job Traveler Reports





Hi,
We need to modify Picklist and Traveler Crystal Reports to add some new
information that are not included in the tables. The tech team told us to
create a new BAQ and derive the reports from them. It seems using ODBC is a
bad idea.
There are no base BAQs for these reports. Before making these from scratch I
wanted to see if anyone has created these before and can give us some
direction.
We are using Epicor 905.605, but I would appreciate older versions to use as
reference.

thanks,





[Non-text portions of this message have been removed]
Hi,
We need to modify Picklist and Traveler Crystal Reports to add some new information that are not included in the tables. The tech team told us to create a new BAQ and derive the reports from them. It seems using ODBC is a bad idea.
There are no base BAQs for these reports. Before making these from scratch I wanted to see if anyone has created these before and can give us some direction.
We are using Epicor 905.605, but I would appreciate older versions to use as reference.

thanks,
You could create a new Report Data Definition and link in the tables you need. I added a few tables related to the customer this way to show some additional info on the customer attached through a sales order demand link.

I then copied and added my modifications to the crystal report and used a report style to make it the default report.

--- In vantage@yahoogroups.com, "cooner_55421" <cooner_55421@...> wrote:
>
> Hi amvarghai,
>
> Just wondering what do you want to add?
>
> >seems using ODBC is a bad idea.
> Yes, there are a lot of reasons not to use ODBC.
>
> But in my case...
> I had to add a LOT of extra tables/fields.
> This was while going live & it was needed right away.
> I made a prototype using ODBC & mfg was happy.
>
> I later converted to BAQ.
> But... it turned out to be slower than the ODBC version.
> People won't use it.
> I've tried improving performance a couple of times, but can't get anywhere close to the speed of the ODBC version. So I'm stuck for now.
> 8.03.409C Progress.
>
> Thanks,
>
> Bruce
>
> --- In vantage@yahoogroups.com, "amvarghai" <amvarghai@> wrote:
> >
> > Hi,
> > We need to modify Picklist and Traveler Crystal Reports to add some new information that are not included in the tables. The tech team told us to create a new BAQ and derive the reports from them. It seems using ODBC is a bad idea.
> > There are no base BAQs for these reports. Before making these from scratch I wanted to see if anyone has created these before and can give us some direction.
> > We are using Epicor 905.605, but I would appreciate older versions to use as reference.
> >
> > thanks,
> >
>