NetTalk Central

Author Topic: Priming  (Read 4424 times)

alan

  • Jr. Member
  • **
  • Posts: 58
    • View Profile
    • Email
Priming
« on: July 11, 2014, 09:55:23 AM »
Hi Bruce,

I have two NetWebForms.  On one, priming works fine.  On the second, priming is not working.

One the form where it's not working, 'Prime for Insert' and 'Prime for Copy' are checked but Disabled.  I see no way to enable them.  Also, this form has 'User must be logged in' set.  That's the only differences I can see between the two forms.

Alan
Alan Schoolcraft

terryd

  • Hero Member
  • *****
  • Posts: 759
    • View Profile
    • Davcomm
    • Email
Re: Priming
« Reply #1 on: July 12, 2014, 11:02:59 AM »
HI Alan
It sounds like this is a netwebform where the form source is set as memory.
If that's right then the default for memory forms is Change which is why the prime for change checkbox can be set.  
If you go to the advanced tab on the form there is a dropdown for the default form action which can be changed to insert.
Currently unless you check the prime for change box no priming will be done.

This presupposes that what I said in the first line a bove is correct. If not please ignore ;-)
« Last Edit: July 12, 2014, 11:10:43 AM by terryd »
Terry Davidson
Windows 10 64 bit/Windows7 64bit
Clarion 9.1.11529/Clarion10 12567
Nettalk 913
Nettalk 1015
StringTheory267/Winevent515/XFiles298/MessageBox239/Cryptonite186

alan

  • Jr. Member
  • **
  • Posts: 58
    • View Profile
    • Email
Re: Priming
« Reply #2 on: July 13, 2014, 06:43:48 AM »
Terry,

Thanks for the reply.  You are correct, they are both memory forms.  I set the offending form to Insert as you suggested.  Unfortunately, that did not enable the prime on insert checkbox.  Although it is checked and disabled, the priming still doesn't work.

Alan
Alan Schoolcraft

terryd

  • Hero Member
  • *****
  • Posts: 759
    • View Profile
    • Davcomm
    • Email
Re: Priming
« Reply #3 on: July 13, 2014, 10:51:43 PM »
Hi Alan.
Is there a reason why you want to do an Insert on a memory form? You are not saving the record, I assume you are  just using the form to store certain variables to be used in limiting a report or browse.
If that's the case I personally would leave the setting as change and check the prime on change box.
Then check the preupdate routine in your form's source code to see that the priming information is there.
 
Terry Davidson
Windows 10 64 bit/Windows7 64bit
Clarion 9.1.11529/Clarion10 12567
Nettalk 913
Nettalk 1015
StringTheory267/Winevent515/XFiles298/MessageBox239/Cryptonite186

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: Priming
« Reply #4 on: July 14, 2014, 12:58:10 AM »
Memory forms are in "change" mode, and hence priming on Insert does not make sense.

cheers
Bruce

alan

  • Jr. Member
  • **
  • Posts: 58
    • View Profile
    • Email
Re: Priming - resolved
« Reply #5 on: July 14, 2014, 08:17:45 AM »
Ok, cool. I didn't realize memory forms were always in change mode.

I got the desired results by checking "Prime for change" and "Only if field is not already set".

Thanks Bruce
Alan Schoolcraft

terryd

  • Hero Member
  • *****
  • Posts: 759
    • View Profile
    • Davcomm
    • Email
Re: Priming
« Reply #6 on: July 14, 2014, 04:29:42 PM »
My pleasure (I think)
Terry Davidson
Windows 10 64 bit/Windows7 64bit
Clarion 9.1.11529/Clarion10 12567
Nettalk 913
Nettalk 1015
StringTheory267/Winevent515/XFiles298/MessageBox239/Cryptonite186