NetTalk Central

Author Topic: How to delete when Form has parameters  (Read 2912 times)

CaseyR

  • Sr. Member
  • ****
  • Posts: 448
    • View Profile
    • Email
How to delete when Form has parameters
« on: April 12, 2011, 07:12:26 PM »
I have a browse/form for some some records that are children of several different entity types.  While the entity members have unique id numbers within each type, there can be duplicate entity numbers between types.  So to ensure the records for the right entity are retrieved or primed, I pass the entity type and entity number as parameters as a manual URL in the Advanced tab.  Works great for Insert and Change, but the parameters seem to interfere with Delete.  When Delete is clicked, the form is called but nothing happens.

I could pass the entity type and id number as session values, but because there are different parent entity types using the same form and browse there may be interference if the user goes on to one task before they finish a previous one.

Is there a way to use parameters for Insert and Change while still being able to Delete?

Many thanks.   

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: How to delete when Form has parameters
« Reply #1 on: April 12, 2011, 08:36:04 PM »
Which Nettalk build?

Also - it sounds like really what you want is multi-component key support for Forms and Deletes. Is that right?

CaseyR

  • Sr. Member
  • ****
  • Posts: 448
    • View Profile
    • Email
Re: How to delete when Form has parameters
« Reply #2 on: April 13, 2011, 11:37:16 AM »
Sorry, using 5.14.

The table in question is an In-Memory table with a unique single component (LONG)  primary key.  It is used to temporarily hold URL's for images and documents associated with different types of entities.   The EntityType and EntityNumber parameters are used for filtering the browse and priming on Insert.  The corresponding fields in the table are not unique values.  No problem creating a three component unique key but I have always thought that wouldn't work for Delete

If you are thinking of adding multi-component key support for the future, I think it is a good idea for those users converting an existing Clarion dictionary for NetTalk.  In my case, I have already created single component primary keys for all my tables.

I have another idea for addressing the issue but it has much broader application so I am posting it as a separate topic.

Thanks.