NetTalk Central

Author Topic: Replicate and NetTalk  (Read 3519 times)

Mike McLoughlin

  • Full Member
  • ***
  • Posts: 126
    • View Profile
    • Clarion Templates
    • Email
Replicate and NetTalk
« on: April 02, 2009, 12:30:02 PM »
All my child files are set up for Replicate with a Site Field (string 4) and a Linkid (long) forming the link-to-parent key.

I can't see anywhere in the Browse template to prime a second key field - is there a workaround for this?  I have a GUID in every file but I want to avoid adding any more key-overhead to the system.

regards

Mike
Mike McLoughlin

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: Replicate and NetTalk
« Reply #1 on: April 02, 2009, 08:33:40 PM »
Hi Mike,


For Replicate to work you need a key on the Guid field anyway.
So add that key. Then that makes the perfect key for browses and forms.

Cheers
Bruce

Mike McLoughlin

  • Full Member
  • ***
  • Posts: 126
    • View Profile
    • Clarion Templates
    • Email
Re: Replicate and NetTalk
« Reply #2 on: April 03, 2009, 12:21:00 AM »
Hi Bruce

I do actually have a key already on each GUID - but what I don't have is a key in the child record linking to the parent's GUID field.  Which is what I think you are suggesting is the way to go.

Have you got any plans to add 2-component key support to browse ranges?

thanks

Mike
Mike McLoughlin

Mike McLoughlin

  • Full Member
  • ***
  • Posts: 126
    • View Profile
    • Clarion Templates
    • Email
Re: Replicate and NetTalk
« Reply #3 on: April 03, 2009, 03:10:24 AM »
Its OK I found a workaround - link to the 2nd key element as File Relationship and then in the browse embed prime the first element (Site) to D000 or whatever it is.

Mike
Mike McLoughlin