Re: Puzzling query problem when combining two blocks into one

[Quoted] Sounds like you're adding additional items to a block, and changing the properties so that two items reference the same column.

Such as:

Item1 = column1
item2 = column1

Interesting concept... Every try select colum1, column1 from table? the database renames the second reference of column1 to some arbitrary name. Forms doesn't seem to understand that concept.

[Quoted] [Quoted] Instead, change Item2 to be non database and set it's Mirror Item value to Item1...

I had a select in a record group that did just this sort of thing (for populating list boxes). Then one day, when I needed to correct the ordering of my query results.

When I tried to save changes to the SQL for the record group, forms GPF'd and GPF'd and GPF'd until I aliased the two column with different names.

"Todd Owers" <toddo_at_gcr1.com> wrote:

> I have a problem that is very puzzling. In Forms 4.5.7.1.6, I created a
> form that had two blocks that were based on the same database table. The
> items in each block were on two different canvases.
>
> I converted the fmb to Forms 5.0.6.8.0., and put the two blocks on different
> tab pages of a tabbed canvas. Then, I realized there was no reason why the
> two blocks could not be combined into one, because they are based on the
> same table. So I moved the items from the second block into the first
> block, then deleted the second block. But this caused a problem with
> queries in the first block. I now get a "FRM-40350: Query caused no records
> to be retrieved" message when executing a query in the first block. Yet
> nothing was changed in the WHERE clause of this block. Strange thing is,
> when I put everything back to the original configuration (two different
> blocks), the queries in the first block work fine!
>
> To summarize: the original configuration had block A containing items 1,2,3,
> and block B containing items 4,5,6. All items are base table items. Query
> in block A works fine. The new configuration has block A containing items
> 1,2,3,4,5,6, and block B is deleted. Nothing changed in WHERE clause.
> Query in block A gives FRM-40350 message.
>
> I do not understand why I am getting FRM-40350. If one of the new items
> added to block A was invalid (e.g. misspelled, or column does not exist in
> that table), then I would expect to receive the "FRM-40505: Oracle error -
> unable to perform query" message. But this is not the case. The addition
> of items to the block should affect only the columns in the SELECT list, not
> the WHERE clause.
>
> The only explanation I can think of is that some quirk occurred during the
> conversion from Forms 4.5 to 5.0. Does anyone have any other ideas?
>
> Thanks in advance for your help.
>
> Todd Owers
> toddo_at_gcr1.com
>
>

--
joebrown
_at_leading.net