Program to clear a particular field in all the records of table

.p is usually faster. But if changing the field calls a special BO method
and/or makes additional changes you're definitely better off doing it
through a customization/BO.

As far as finding the ramifications of a field change, there really isn't
an easy way. You can take apart the BOs and see what they do, or you can
take a test database, and check things before/after the change. Neither is
particularly fun.

*John Driggers*
**
*Chief Data Wrangler*
*
*
*I have an Epicor blog <http://usdoingstuff.com/>. How useful is that?*
*
*:: 904.404.9233
:: waffqle@...
:: http://www.usdoingstuff.com <http://www.usdoingstuff.com/>

*

*



On Tue, Sep 25, 2012 at 10:25 AM, c.krusen1 <ckrusen1@...> wrote:

> **
>
>
> I want to create a program to clear the TaxCatID field for all parts in
> the Part table. BTW, we have the OpenEdge DB.
>
> 1. How can you determine if changes to a field causes other actions? For
> example, Changing a Part's Product ProdCode, automatically changes the
> TaxCatID to that of the one for that ProdCode.
>
> 2. Would you recommend creating a .p program and running it from the
> Progress Tools on the server, or customize a screen to run it once, and
> then remove the customization?
>
> Calvin
>
>
>


[Non-text portions of this message have been removed]
I want to create a program to clear the TaxCatID field for all parts in the Part table. BTW, we have the OpenEdge DB.


1. How can you determine if changes to a field causes other actions? For example, Changing a Part's Product ProdCode, automatically changes the TaxCatID to that of the one for that ProdCode.

2. Would you recommend creating a .p program and running it from the Progress Tools on the server, or customize a screen to run it once, and then remove the customization?

Calvin