Putting Customization into a tracker

Yahoo Archive
1
Unless you are an xml wiz, (and would be comfortable selectively moving huge sections of exported xml from a Tracker's brethren Maintenance app into an xml export of the Tracker) - I suggest you just recreate your changes.

--- On Thu, 7/24/08, brad.ebright <bebright@...> wrote:

From: brad.ebright <bebright@...>
Subject: [Vantage] Re: Putting Customization into a tracker
To: vantage@yahoogroups.com
Date: Thursday, July 24, 2008, 9:30 AM






I also need to know how to put the customization into the tracker. do
we have to redo the screen on can we export and import it?

--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
wrote:
>
> Unless these a key fields (that might be direct entry or searchable
fields that need a value pre-entered in order for the tracker to
update and display) - all Tracker fields are essentially read-only
& 'greyed out' - which is different from disabled.
>
> Disabled controls (wrapped around the table.field) sometimes result
in an error when you clear the screen and the record row goes to -
1... Additional If/Then code is needed in a suitably triggered Sub to
prevent the errors.
>
> If you MUST make them ReadOnly=False and Enabled=True, you can use
the ExtendedProperties modifier upon form load (or record load -
depending upon what conditions you want the fields activated for the
appearance of being editable - even if the Tracker contains no
adapter and assemblies to allow db writes).
>
> Rob Brown
>
> --- On Wed, 7/23/08, brad.ebright <bebright@.. .> wrote:
> From: brad.ebright <bebright@.. .>
> Subject: [Vantage] Putting Customization into a tracker
> To: vantage@yahoogroups .com
> Date: Wednesday, July 23, 2008, 3:57 PM
>
>
>
>
>
>
>
>
>
>
>
> We have made a customization to the order entry screen
and would like
>
> to put it in the tracker, but with the fields greyed out. How do we
do
>
> this. We are running 8.0
>
>
>
> Thanks for you help,
>
> Brad
>
2
We have made a customization to the order entry screen and would like
to put it in the tracker, but with the fields greyed out. How do we do
this. We are running 8.0

Thanks for you help,
Brad
3
Unless these a key fields (that might be direct entry or searchable fields that need a value pre-entered in order for the tracker to update and display) - all Tracker fields are essentially read-only & 'greyed out' - which is different from disabled.

Disabled controls (wrapped around the table.field) sometimes result in an error when you clear the screen and the record row goes to -1... Additional If/Then code is needed in a suitably triggered Sub to prevent the errors.

If you MUST make them ReadOnly=False and Enabled=True, you can use the ExtendedProperties modifier upon form load (or record load - depending upon what conditions you want the fields activated for the appearance of being editable - even if the Tracker contains no adapter and assemblies to allow db writes).

Rob Brown

--- On Wed, 7/23/08, brad.ebright <bebright@...> wrote:
From: brad.ebright <bebright@...>
Subject: [Vantage] Putting Customization into a tracker
To: vantage@yahoogroups.com
Date: Wednesday, July 23, 2008, 3:57 PM











We have made a customization to the order entry screen and would like

to put it in the tracker, but with the fields greyed out. How do we do

this. We are running 8.0



Thanks for you help,

Brad
4
Rob, you mentioned putting using extended properties upon form load or
record load. How do I set it to run upon record load? I have been using
EpiViewNotification>Initialize to run my "record load" customizations but I
don't like that method too much because that method runs many times for each
record change. Is there a better solution for running customizations every
time new records get loaded?



Daniel

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Robert Brown
Sent: Thursday, July 24, 2008 3:07 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Putting Customization into a tracker



Unless these a key fields (that might be direct entry or searchable fields
that need a value pre-entered in order for the tracker to update and
display) - all Tracker fields are essentially read-only & 'greyed out' -
which is different from disabled.

Disabled controls (wrapped around the table.field) sometimes result in an
error when you clear the screen and the record row goes to -1... Additional
If/Then code is needed in a suitably triggered Sub to prevent the errors.

If you MUST make them ReadOnly=False and Enabled=True, you can use the
ExtendedProperties modifier upon form load (or record load - depending upon
what conditions you want the fields activated for the appearance of being
editable - even if the Tracker contains no adapter and assemblies to allow
db writes).

Rob Brown

--- On Wed, 7/23/08, brad.ebright <bebright@mgsmail.
<mailto:bebright%40mgsmail.com> com> wrote:
From: brad.ebright <bebright@mgsmail. <mailto:bebright%40mgsmail.com> com>
Subject: [Vantage] Putting Customization into a tracker
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Date: Wednesday, July 23, 2008, 3:57 PM

We have made a customization to the order entry screen and would like

to put it in the tracker, but with the fields greyed out. How do we do

this. We are running 8.0

Thanks for you help,

Brad
















[Non-text portions of this message have been removed]
5
I also need to know how to put the customization into the tracker. do
we have to redo the screen on can we export and import it?

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:
>
> Unless these a key fields (that might be direct entry or searchable
fields that need a value pre-entered in order for the tracker to
update and display) - all Tracker fields are essentially read-only
& 'greyed out' - which is different from disabled.
>
> Disabled controls (wrapped around the table.field) sometimes result
in an error when you clear the screen and the record row goes to -
1... Additional If/Then code is needed in a suitably triggered Sub to
prevent the errors.
>
> If you MUST make them ReadOnly=False and Enabled=True, you can use
the ExtendedProperties modifier upon form load (or record load -
depending upon what conditions you want the fields activated for the
appearance of being editable - even if the Tracker contains no
adapter and assemblies to allow db writes).
>
> Rob Brown
>
> --- On Wed, 7/23/08, brad.ebright <bebright@...> wrote:
> From: brad.ebright <bebright@...>
> Subject: [Vantage] Putting Customization into a tracker
> To: vantage@yahoogroups.com
> Date: Wednesday, July 23, 2008, 3:57 PM
>
>
>
>
>
>
>
>
>
>
>
> We have made a customization to the order entry screen
and would like
>
> to put it in the tracker, but with the fields greyed out. How do we
do
>
> this. We are running 8.0
>
>
>
> Thanks for you help,
>
> Brad
>
6
Using Row Rules (suggest you use the wizard for this as the resulting code isn't always very intuitive) is the most reliable - but the table field you want to affect must be conveniently within the same table (but perhaps another field) with which your event trigger occurs.

When all else fails, use brute force (and forget about flaky EpiNotification triggers):

Example:

Sub InitializeCustomCode()

'// ** Wizard Insert Location
'// Begin Wizard Added Variable Intialization
'// End Wizard Added Variable Intialization

'// Begin Custom Method Calls
'// End Custom Method Calls
SetExtendedProps()
End Sub

Private Sub SetExtendedProps()

Dim edvJO As EpiDataView = CType(oTrans.EpiDataViews("JobOper"), EpiDataView)

If edvJO.dataView.Table.Columns.Contains("OpComplete") Then

edvJO.dataView.Table.Columns("OpComplete").ExtendedProperties("ReadOnly") = False

End If

End Sub

Calling a Sub like this in the InitCustCode section makes it active in the app as soon as a record is pulled in from the Table.Column you are trying to change the properties of.

In this case (a snippet from our Job Entry) - it allows the planner to over-ride an OP and mark it complete (via a custom checkbox control) by making the normally read-only column editable.

Very handy...

Rob Brown


--- On Thu, 7/24/08, Daniel Laidig <daniellaidig@...> wrote:

From: Daniel Laidig <daniellaidig@...>
Subject: RE: [Vantage] Putting Customization into a tracker
To: vantage@yahoogroups.com
Date: Thursday, July 24, 2008, 7:19 AM






Rob, you mentioned putting using extended properties upon form load or
record load. How do I set it to run upon record load? I have been using
EpiViewNotification >Initialize to run my "record load" customizations but I
don't like that method too much because that method runs many times for each
record change. Is there a better solution for running customizations every
time new records get loaded?

Daniel

_____

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf Of
Robert Brown
Sent: Thursday, July 24, 2008 3:07 AM
To: vantage@yahoogroups .com
Subject: Re: [Vantage] Putting Customization into a tracker

Unless these a key fields (that might be direct entry or searchable fields
that need a value pre-entered in order for the tracker to update and
display) - all Tracker fields are essentially read-only & 'greyed out' -
which is different from disabled.

Disabled controls (wrapped around the table.field) sometimes result in an
error when you clear the screen and the record row goes to -1... Additional
If/Then code is needed in a suitably triggered Sub to prevent the errors.

If you MUST make them ReadOnly=False and Enabled=True, you can use the
ExtendedProperties modifier upon form load (or record load - depending upon
what conditions you want the fields activated for the appearance of being
editable - even if the Tracker contains no adapter and assemblies to allow
db writes).

Rob Brown

--- On Wed, 7/23/08, brad.ebright <bebright@mgsmail.
<mailto:bebright% 40mgsmail. com> com> wrote:
From: brad.ebright <bebright@mgsmail. <mailto:bebright% 40mgsmail. com> com>
Subject: [Vantage] Putting Customization into a tracker
To: vantage@yahoogroups <mailto:vantage% 40yahoogroups. com> .com
Date: Wednesday, July 23, 2008, 3:57 PM

We have made a customization to the order entry screen and would like

to put it in the tracker, but with the fields greyed out. How do we do

this. We are running 8.0

Thanks for you help,

Brad

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