Some Advice Understanding RTM File Please

rbuser

Hi guys not sure this is right forum but here goes..

I have an End User solution with custom Autosearch as per the standard
guidelines.

Here is the problem.

Recently I have had reports written and then when the search criteria is
modified the AutoSearch form goes all wrong. For Example..

If I had a report with say three autosearch fields with default values set

AS1 like A%
AS2 > 10
AS3 like B%

I get the autosearch box correctly. If I then remove AS2 and add two more
like this

AS1 like A%
AS3 like B%
AS4 > 20
AS5 = 10

what happens is that the autosearch labels are all wrong they seem to go out
of order or remain in the original order that they were set.

So I thought I would look at the RTM file to see if I could see the problem
but could not.

Any help would be greatly appreciated

Cheers

Mark

nicocizik

Hi Mark,

How are the autosearch labels incorrect? You mention that you are using a
custom autosearch dialog. Does the same behavior occur when you use the
default autosearch dialog? Which version of ReportBuilder are you using?

--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com

rbuser

Nico

For example I have a report an autosearch is set on a filed called
Inspection Date.
The auto search label says something like "Where the Inspection Date is
greater than"

If I then change this to be say an autosearch on a field called Sales Date
the autosearch label still says "Where the Inspection Date is greater than"
but the report is correctly seatched by Sales Date.

Does that make sense ? It seems that the order in which the Autosearch
Fields appear on the Autosearch Form can be set once when the Report is
first created but if you modify the report as described above the whole
thing goes wrong (only the labels)!!!

So I thought if I looked at the RTM file I could see (or get clues) as to
what order the labels and fields are being drawn on the autossearch forms.

Any pointers?


Cheers

Mark

rbuser

Nico

I want to add some more. The report in question that we are having problems
with was created from another report. This report did have two data sets
with autosearch on each of them.

I did not need two datasets for the new report so removed the join and then
deleted the dataset.

So now I have one dataset. The report runs fine in preview.

When I run from the Explorer the first autosearch label is referring to a
field that was on the now DELETED dataset. The report runs fine its just the
labels are referring to an autosearch field that used to be there when the
second dataset was present.

Does that give any more clues?

Cheers

Mark

nicocizik

Hi Mark,

In my testing, I am unable to recreate this behavior. Changing one or many
Autosearch fields correctly changes them in the Autosearch dialog. It may
be that this removed dataset has somehow corrupted your template. You might
try creating a new report only using the dataset you need (very simple at
first) and see if that solves the problem.

--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com

rbuser

Nico
. I too hae tried a simple report and could not re-produce it. My custom
autosearch produces combo box drop downs and they appeared in correct place
with correct labels.

So my question is where in the RTM file is the order of the search fields
stored (and perhaps the order of the labels). Can I manipulate this in any
way so that I dont have to re-do the report. Its quite big and has RAP etc.

Cheers

Mark

nicocizik

Hi Mark,

All the criteria that is created is saved in the template however none of
the AutoSearch Fields are. If you take a look at a template in ascii format
you will see that the TdaCriteria object has an AutoSearch property. If
this is true, then an AutoSearch field is created and used in the report.
You might take a look at the criteria defined in your template to be sure
anything unused is not trying to create an AutoSearch field but this may
cause even more problems. The sure-fire way to solve this problem is to
recreate the report from scratch.

--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com