This topic is locked

Hyperlink lookup

6/5/2004 2:51:21 AM
ASPRunnerPro General questions
T
Toad author

In your formatting page you have an option for "Hyperlink". How do I point this link to another table (or view) in the same way that you use master detail functionality.
As an example I have the following tables

tbl.Orders: OrderID, AttemptID,ContractID etc

tbl.Attempt:AttemptID,EventID etc

tbl.EventId: EventID, etc
(Orders is linked with Attempt, Attempt links with Event)
Now it would be great if in tbl.Orders I could select an AttemptID and it would open up the Attempts table and show records for that AttemptID.
Is this possible within ASPRunner. And if not could you suggest how I modify the ASP files to accomodate such behaviour.
Additionally, how difficult would it be to set up a seperate search option that would allow me to select all orders for an EventID. Because these tables are not linked directly this is not possible in your present search screen. All it would require is a predefined view and the ability to enter in an EventID.
Thanks.

Sergey Kornilov admin 6/8/2004

Toad,
you can use master-detail relationship for this purpose. Choose Orders as a Master table and Attempts as a Detail table. Use AttemptID as both primary and foreign keys.
Answering your second question I would recommend to create an additional view or query in the database that combines data from all three tables ( via INNER JOIN ). Run ASPRunner against this view to create a search page where you can search by EventID.

T
Toad author 6/9/2004

I see your point about the master detail relationship.

you can use master-detail relationship for this purpose. Choose Orders as a Master table and Attempts as a Detail table. Use AttemptID as both primary and foreign keys.


As I understand it however, in ASP runner pro a table can only be detail for "one" other table.
Is there a way that the Events table can be detail for both Orders and Attempts?
Thanks.

Sergey Kornilov admin 6/13/2004

Toad,
you are right, each table can be Detail just for one Master table.
To workaround this limitation I would suggest to create a view/query on the top of Detail table and create an additional relationship using this view.
I hope this helps.