I need to change a field's length in a SQL Server DB table from 4 char to 8. Does anyone know if I need to delete all current reports generated in Development Studio that call this table and recreate them to use the new/revised table or is there a way I can keep the reports and just recompile/refresh to bring in the new table somehow?

Thank you for helping.

This message has been edited. Last edited by: Kathleen Butler,

Your first step, after the database schema is actually changed, is to refresh the synonym so that the .mas file correctly represents the data.

Now it may get a bit tedious, but there is no way to get around it. If a report simply displays the field, then you probably will not have to do anything other than to verify the styling.

If a report uses that field in any COMPUTE or DEFINE, you will have to analyze how it is being used and if it will cause that COMPUTE or DEFINE to fail. The same holds true if the field is saves to an alpha file and a -READ is used to put the value into an amper variable.

Good luck.

And you can use the impact analysis functionality that comes with DevStudio to find out which fexes use that particular field from that particular master file.

quote:

Originally posted by GamP:
And you can use the impact analysis functionality that comes with DevStudio to find out which fexes use that particular field from that particular master file.

isn't that only available in Resource Analyzer addon?

- ABT

If you have access to the reporting server console you can use the Impact Analysis utility to find the field that changed in every synonym/procedure that it is used, and see how it is used. The utility is precisely for isolating the impact of a change to a field/table, etc. From the web console, you can right-click an application directory and you will see the option for Impact Analysis.

It's also in DevStudio, regardless of RA/RG.
You'd have to be in the master folder and right click the master to see the Impact Analysis option. The master has to be added to the project though.

you're on a windows server...
so with a drive mapped to your server...
use TEXTPAD (http://www.textpad.com)
navigate to the directory(ies) where your fexes are, and
do a FIND IN FILES and search for the string that is your filename
TEXTPAD will tell you what fexes call your file, and the line numbers in those fexes.
in those fexes, change the fieldname(s) in question.
This works if you're writing directly in SQL or with masters using FOCUS code.

quote:

Originally posted by susannah:
you're on a windows server...
so with a drive mapped to your server...
use TEXTPAD (http://www.textpad.com)
navigate to the directory(ies) where your fexes are, and
do a FIND IN FILES and search for the string that is your filename
TEXTPAD will tell you what fexes call your file, and the line numbers in those fexes.
in those fexes, change the fieldname(s) in question.
This works if you're writing directly in SQL or with masters using FOCUS code.

You've described 25% of my job in the lines above.

Hi all,

I finally got the issue fixed. The problem was that the revised/corrected joints were not reflected in the reports automatically so they have to be changed manually before correct data can be extracted.

Thanks again. Hope y'all have a great day.

Kim