BAQ Creation issues (V 8.03)

Yahoo Archive
1
I have found this issue too - mostly when you have more than one calculated field and you move, delete, change one of those calc fields...Lately, I have found when I work with these if I change one - others are displayed incorrectly as CalcField - 2 etc, but I can close and reopen and they will be back as they should be...So, I only change one calc field at a time, then save, close/reopen...

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of c.krusen1
Sent: Friday, August 26, 2011 2:39 PM
To: vantage@yahoogroups.com
Subject: [Vantage] BAQ Creation issues (V 8.03)



I'm having promblems creating and maintaining BAQs. The problem isn't with the data results, but the actual BAQ Entry screen. I occasionally get fields in the Display Columns that are FUBAR'd and I can't delete them. This happens most often when I use a calculated field, or when I re-order the fields. It can happen to a BAQ that has just one table referenced.

I have a BAQ named MC-DateTest, that has just the PartTran table. The Display Columns shows two fields "PartTran.TranDate" and "CalcField-2". I never created a field named "CalcField-2", and if I move it up above the .TranDate field, its name changes to "CalcField-1".

I created a BAQ of the QueryCalcFld table and saw something odd.

There are two QueryCalcFld records with the ExportID=MC-DateTest, which are identical except for the "Approved" field.

I have no idea what sets/clears the "Approved" field, and why I have the same exact line with both an approved and a non-approved setting.



[Non-text portions of this message have been removed]
2
I'm having promblems creating and maintaining BAQs. The problem isn't with the data results, but the actual BAQ Entry screen. I occasionally get fields in the Display Columns that are FUBAR'd and I can't delete them. This happens most often when I use a calculated field, or when I re-order the fields. It can happen to a BAQ that has just one table referenced.

I have a BAQ named MC-DateTest, that has just the PartTran table. The Display Columns shows two fields "PartTran.TranDate" and "CalcField-2". I never created a field named "CalcField-2", and if I move it up above the .TranDate field, its name changes to "CalcField-1".

I created a BAQ of the QueryCalcFld table and saw something odd.

There are two QueryCalcFld records with the ExportID=MC-DateTest, which are identical except for the "Approved" field.

I have no idea what sets/clears the "Approved" field, and why I have the same exact line with both an approved and a non-approved setting.
3
Yes, the BAQ designer in 8.03 is full of bugs and memory leaks.
Â
The only way to fix a BAQ when something like what you described happens, is to export it to XML and then deleted the offending field then import it back into the BAQ.
Â
I also leaned not to work in the BAQ for any long period of time. I usually save every 5 minutes and after about 20 minutes I exit out and launch it again. Otherwise, it has a tendency to lock up when you try to exit or save.

From: c.krusen1 <ckrusen1@...>
To: vantage@yahoogroups.com
Sent: Friday, August 26, 2011 3:39 PM
Subject: [Vantage] BAQ Creation issues (V 8.03)


Â
I'm having promblems creating and maintaining BAQs. The problem isn't with the data results, but the actual BAQ Entry screen. I occasionally get fields in the Display Columns that are FUBAR'd and I can't delete them. This happens most often when I use a calculated field, or when I re-order the fields. It can happen to a BAQ that has just one table referenced.

I have a BAQ named MC-DateTest, that has just the PartTran table. The Display Columns shows two fields "PartTran.TranDate" and "CalcField-2". I never created a field named "CalcField-2", and if I move it up above the .TranDate field, its name changes to "CalcField-1".

I created a BAQ of the QueryCalcFld table and saw something odd.

There are two QueryCalcFld records with the ExportID=MC-DateTest, which are identical except for the "Approved" field.

I have no idea what sets/clears the "Approved" field, and why I have the same exact line with both an approved and a non-approved setting.




[Non-text portions of this message have been removed]