Date field changed to read only after edit for specific Order Re

Yahoo Archive
1
Robert Brown...



I tried your solution with the checkbox; however, after linking it to field
or not linking it to a field..the changes on a release number 1 for a
particular line number is reflected on the next release number 2. My major
problem is understanding what would allow a field to be tied to the current
record line number and or release number.







Best Regards,



Herby Dallard

Information Technology Engineer

Endicott Research Group

hdallard@...

607-754-9187 ext. 3078

www.ergpower.com







_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Robert Brown
Sent: Wednesday, September 02, 2009 12:50 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] date field changed to read only after edit for
specific Order Release Number





There are probably a myriad of ways to do this, but why not mirror your
initially entered date into a readily available table date## field (only
mirroring the date when it is initially null). Then you could trap attempted
changes to the 'real' date field and, if new value is different than
original mirrored value, halt the update and restore the original date from
the mirrored value.

You could do something similar with checkboxes that would be set to true
after the 'real' date is changed from a date.null to a valid date.

Or, (thinking this through as I'm typing), directly trap updating of an
attempted change to a 'real' (already initially established) date if the
field already contained a non-null date.

The trouble with all of this is that humans make entry mistakes... By doing
this (no matter what the method), you're cutting off the ability of users to
fix entry errors on the fly (unless you give them an over-ride capability
via a toolbox added button control press event).

Change logging the field and the 'honor system' isn't sufficient? (Sure is
easier!... Just have to manage it and use it to reinforce training when
needed & take more final management steps when its a person that just
doesn't care enough to TRY and follow the company's process rules.)

Rob Brown

________________________________
From: herbydallard <hdallard@ergpower. <mailto:hdallard%40ergpower.com> com>
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Sent: Tuesday, September 1, 2009 4:24:59 PM
Subject: [Vantage] date field changed to read only after edit for specific
Order Release Number

I Need help...

I am having problems making a date field read only after it has been edited.
My code works, however, I am trying to ensure the date field
is read only after it has been edited in the Sales Order Entry transaction
>Order Release Number tab.

The problem occurs when an order has multiple release numbers, once an edit
has occurred on the first release number, the next order release number(s)
for the same order line date field becomes read-only.

How can I make the read only on first edit of date field specific to order
release number(s)?

(FYI: I am using allowedit property )

thanks

Best Regards,

Herby Dallard
Information Technology Engineer
Endicott Research Group
hdallard@ergpower. com
607-754-9187 ext. 3078
www.ergpower. com

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
2
I Need help...

I am having problems making a date field read only after it has been edited. My code works, however, I am trying to ensure the date field
is read only after it has been edited in the Sales Order Entry transaction >Order Release Number tab.

The problem occurs when an order has multiple release numbers, once an edit has occurred on the first release number, the next order release number(s) for the same order line date field becomes read-only.

How can I make the read only on first edit of date field specific to order release number(s)?

(FYI: I am using allowedit property )

thanks

Best Regards,

Herby Dallard
Information Technology Engineer
Endicott Research Group
hdallard@...
607-754-9187 ext. 3078
www.ergpower.com
3
There are probably a myriad of ways to do this, but why not mirror your initially entered date into a readily available table date## field (only mirroring the date when it is initially null). Then you could trap attempted changes to the 'real' date field and, if new value is different than original mirrored value, halt the update and restore the original date from the mirrored value.

You could do something similar with checkboxes that would be set to true after the 'real' date is changed from a date.null to a valid date.

Or, (thinking this through as I'm typing), directly trap updating of an attempted change to a 'real' (already initially established) date if the field already contained a non-null date.

The trouble with all of this is that humans make entry mistakes... By doing this (no matter what the method), you're cutting off the ability of users to fix entry errors on the fly (unless you give them an over-ride capability via a toolbox added button control press event).

Change logging the field and the 'honor system' isn't sufficient? (Sure is easier!... Just have to manage it and use it to reinforce training when needed & take more final management steps when its a person that just doesn't care enough to TRY and follow the company's process rules.)

Rob Brown









________________________________
From: herbydallard <hdallard@...>
To: vantage@yahoogroups.com
Sent: Tuesday, September 1, 2009 4:24:59 PM
Subject: [Vantage] date field changed to read only after edit for specific Order Release Number


I Need help...

I am having problems making a date field read only after it has been edited. My code works, however, I am trying to ensure the date field
is read only after it has been edited in the Sales Order Entry transaction >Order Release Number tab.

The problem occurs when an order has multiple release numbers, once an edit has occurred on the first release number, the next order release number(s) for the same order line date field becomes read-only.

How can I make the read only on first edit of date field specific to order release number(s)?

(FYI: I am using allowedit property )

thanks

Best Regards,

Herby Dallard
Information Technology Engineer
Endicott Research Group
hdallard@ergpower. com
607-754-9187 ext. 3078
www.ergpower. com







[Non-text portions of this message have been removed]
4
Thanks Robert. I will try your recommended solution and see which one works
for me. thanks







Best Regards,



Herby Dallard

Information Technology Engineer

Endicott Research Group

hdallard@...

607-754-9187 ext. 3078

www.ergpower.com







_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Robert Brown
Sent: Wednesday, September 02, 2009 12:50 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] date field changed to read only after edit for
specific Order Release Number





There are probably a myriad of ways to do this, but why not mirror your
initially entered date into a readily available table date## field (only
mirroring the date when it is initially null). Then you could trap attempted
changes to the 'real' date field and, if new value is different than
original mirrored value, halt the update and restore the original date from
the mirrored value.

You could do something similar with checkboxes that would be set to true
after the 'real' date is changed from a date.null to a valid date.

Or, (thinking this through as I'm typing), directly trap updating of an
attempted change to a 'real' (already initially established) date if the
field already contained a non-null date.

The trouble with all of this is that humans make entry mistakes... By doing
this (no matter what the method), you're cutting off the ability of users to
fix entry errors on the fly (unless you give them an over-ride capability
via a toolbox added button control press event).

Change logging the field and the 'honor system' isn't sufficient? (Sure is
easier!... Just have to manage it and use it to reinforce training when
needed & take more final management steps when its a person that just
doesn't care enough to TRY and follow the company's process rules.)

Rob Brown

________________________________
From: herbydallard <hdallard@ergpower. <mailto:hdallard%40ergpower.com> com>
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Sent: Tuesday, September 1, 2009 4:24:59 PM
Subject: [Vantage] date field changed to read only after edit for specific
Order Release Number

I Need help...

I am having problems making a date field read only after it has been edited.
My code works, however, I am trying to ensure the date field
is read only after it has been edited in the Sales Order Entry transaction
>Order Release Number tab.

The problem occurs when an order has multiple release numbers, once an edit
has occurred on the first release number, the next order release number(s)
for the same order line date field becomes read-only.

How can I make the read only on first edit of date field specific to order
release number(s)?

(FYI: I am using allowedit property )

thanks

Best Regards,

Herby Dallard
Information Technology Engineer
Endicott Research Group
hdallard@ergpower. com
607-754-9187 ext. 3078
www.ergpower. com

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]