OK...
Some coworkers and I were having a discussion on some development project we are working on.

It involves adding a new column to a custom table we use.

The table (Lets call it "tisfc999") currently contains 5 columns - we will add a 6th.

Person A Says:

We need to perform a "Where Used Report" on the table name to find all sessions/scripts/DLL's that access the table and re-compile them. Otherwise - any program that uses SQL in the following format:

Select tisfc999.*
from tisfc999
where........

Will not return the correct data because of the table change.


Person B Says:

That shouldn't be the case - identifying and re-compiling some 200 sessions/scripts/DLL's that access this table will be a waste of time and is not required.


Since neither person would budge on their opinion - I wanted to post the question to www.baanboard.com and get some opinions and answers.

If you changed an existing field or index, you might need to alter and recompile you script, but simply adding a field will not force such an action. I've done this many times.

Person B is right.