Next, go to find in Contacts

This step essentially replicates what was done in finding the appropriate records within the Friends table, and, then imports them into the SearchReturn table.

Viewing the returned records in SearchReturn

Finally, the result in the SearchReturn table is this.

Returning to the chosen record in its native table

To view the chosen record in the table from which it came, you need to set up the following script. In simple terms, the steps for this comprise:

  1. Setting the global fields to fulfil the 'return' search.
  2. Finding and deleting the found records in the SearchReturn table, as these are no longer of value, once you have decided which record you wish to view.
  3. Navigating to the correct layout (and table) by its designation in gLayoutCatcher.
  4. Finding the right record in that layout by the match on gIDcatcher with the record's ID, to create the occurrence of '1' in cIfMatchgIDcatcher in the 'home' table.
  5. Clearing the global fields of their values as a matter of good housekeeping in preparation for the next search.

These steps are illustrated exactly in the script definition beneath.

Finally, to execute this return search, you may wish to make the 'view' text shown above on the ReturnSearch layout into a clickable button, which you can do as shown beneath by selecting the text in Layout Mode, then using Insert>button and following the steps to attach it to the script above.

Adaptable

Depending on your purposes and the size and structure of your database, there are myriad embellishments you may wish to make to this solution. Nevertheless, its main value is that of isolating, through the use of the temporary set of values in the SearchReturn table, the discrete set of records which meet your specific interest.

Do you need help with Mac? Gain advice from Builder AU forums

Related links

Comments

1

Emile - 13/07/06

OOoooo, this is a great technique. Is there any way you can provide a sample file download to better illustrate how it works? Thanks

» Report offensive content

2

ianj - 03/10/06

One quick comment about the table names. Using a "." character in a table name or a field name has the potential to cause untold grief if you need to web-enable the system or connect via ODBC/JDBC. It's generally a really bad idea.

ian

» Report offensive content

3

Ender - 25/11/06

I'm afraid I don't see the need for techniques like this that search across multiple tables. Tables should really be about different things. If you have two tables with similar types of things, then the tables should probably be combined (especially if they may need to be shown together in a common listing or report).

In this example, "Friends" and "Contacts" should really reside in the same table, with a Contact Type field used to distinguish between them. This structure would make this search and listing quite simple, with no additional tables or import scripts required.

» Report offensive content

4

yusuf alam - 24/01/07

I want to search the record from the existing table from the oracle database using visualbasic programe and it will display the result in to the text box
select * from student where st_roll =" ' text1.text ' "

» Report offensive content

Leave a comment

You must read and type the 6 chars within 0..9 and A..F

* indicates mandatory fields.

4

yusuf alam - 24/01/07

I want to search the record from the existing table from the oracle database using visualbasic programe and it will display ... more

3

Ender - 25/11/06

I'm afraid I don't see the need for techniques like this that search across multiple tables. Tables should really be ... more

2

ianj - 10/03/06

One quick comment about the table names. Using a "." character in a table name or a field name has the ... more

Log in


Sign up | Forgot your password?

  • Staff Microsoft shows off IE9 preview

    This week, highlights from Microsoft's MIX10 conference and more in the Roundup. Read more »

    -- posted by Staff

  • Chris Duckett IE9's H.264 vote killed Ogg

    In a split decision by the judges, the winner of the W3C/WHATWG video codec consensus is H.264, taking home the future of video playback on the internet while loser Ogg goes home with nothing but thoughts of what might have been. Read more »

    -- posted by Chris Duckett

  • Staff Google launches Apps Marketplace

    Google launches and app store, while Mozilla plans to re-write its open-source license. More of this week's news in the Roundup. Read more »

    -- posted by Staff

What's on?

  • Optus Deal

    Broadband + home phone + PlayStation®3 in a single package price!