Is there still a bug with attached retrieve specs in reports? I know there was a problem in an earlier version, if a sort spec was used.

The problem I'm having is, if I attach a retrieve spec that includes an entry in a subform, the report finds no results. The same exact spec loaded manually (provided the spec has been un-attached from the report), produces results as expected.

Quote:

It fails to find anything.

There are no results found whenever any criteria (in one or two elements) is placed in the subform, whether or not there is anything placed in the main form.

Here are the various combinations of entries I tested:
1) Test1 - 1 in main form, 1 in subform
2) Test2 - 1 in subform
3) Test3 - 1 in main form
4) Test4 - 2 in main form
5) Test5 - 2 in subform

Tests 1, 2, & 5 all failed to find any results. You'll notice that each of those contain at least one entry in the subform.

I did use these same saved specs to run a search to verify that they actually produce results.

Erika,

I just discovered a VERY serious problem related to this!

Some of the subforms have had their data replaced with the retrieve specs. For example, one of the retrieve specs were "..dsi..". After running the report that had this spec attached, a subform now has ..dsi.. in an element that used to have other data. Another element ended up with /= in place of a number that was there before.

It seems to hit random subforms. In other words, it doesn't hit the subform that actually contained the spec within it's contents.

Quote:

Yes. I'm the only one that uses it. Besides that, one of the elements is automatically filled with a value upon exiting it, and it had "/=" in it after running the report. Another element that had "..dsi.." in it, brings up a userselect menu upon element entry, so I am pretty sure I would have noticed if I were in update mode.

Unfortunately, I cannot seem to recreate that problem. I'll let you know if I can figure out what conditions caused it.

Hello Carl,

Just to let you know, we have been able to reproduce the behavior, and are looking into it now.

Whoa! I just discovered how to recreate the problem.

It was not while running the report. It was while testing the retrieve specs in search mode to verify that those specs actually should be finding records.

The retrieve specs actually REPLACED the values in the subform elements when leaving the search mode by pressing F10!

I'll document the steps, and send it to support.

You can replicate both problems?

Just to make sure we are talking about the same thing...

I am seeing the problem when I get to search mode by pressing F7 from update mode, then use Alt-F8 to load a retrieve spec with subform criteria, and run the search.

The record that was being viewed when F7 was pressed, will have it's subform elements replaced with the retrieve specs.

Is that the same thing that you have found?