× Discuss about Archiving, Close of Business, Delivery Setup, Security Management System, Global Processing etc…

Adding local field in execution of orders

  • assiddiqui
  • Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 120
  • Thank you received: 0

assiddiqui created the topic: Adding local field in execution of orders

File Attachment:

File Name: VERSION.doc
File Size:73 KB

I want to add a local field in version SC.EXE.SEC.ORDERS,PMB.BROK which will show for each block when i expand the record. Version and Snapshot attached.
#16788
Attachments:

Please Log in or Create an account to join the conversation.

  • armin
  • armin's Avatar
  • Offline
  • Elite Member
  • Elite Member
  • “So long - and thanks for all the fish!”
  • Posts: 300
  • Karma: 13
  • Thank you received: 57

armin replied the topic: Adding local field in execution of orders

can't see anything attached

using R11 on Unix
#16790

Please Log in or Create an account to join the conversation.

  • assiddiqui
  • Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 120
  • Thank you received: 0

assiddiqui replied the topic: Adding local field in execution of orders

File attached.
#16793

Please Log in or Create an account to join the conversation.

  • Posts: 2845
  • Karma: 512
  • Thank you received: 647

jpb replied the topic: Adding local field in execution of orders

You can't place a local field into a core MV set, it will always be separated and so not automatically expanded when you insert a new broker.

You can try to use a reserve field out of the broker MV set by changing the T-array of the field (e.g. with a AUT.NEW.CONTENT routine attached to BROKER.NO).
The input to this field could be moved to the local field with a validation routine and before the record is displayed the value can be filled from local field to the RESERVED in a CHECK.REC.RTN.

But this is dangerous as you never know when the field will be used by TMN and then you will loose your dev.
#16796

Please Log in or Create an account to join the conversation.

Time to create page: 0.181 seconds