This would be a view left over from a join form. Join forms create a T,H,B view and then created the named view on top of the schemaid/fieldid view. You could see if another uncompiled view exists that references this view or T384 view. That would tell you the name of the form and the names of the fields. If not, look at the DDL of the T384 view if it exists, this will tell you what the join was against.
The DDL of the B384 view may tell you what the join was against, but I'm not sure the setructure of the B views without looking. Axton Grams On 2/16/07, Lammey, Peter A. <[EMAIL PROTECTED]> wrote:
** We have been working on installing and testing patch 20 on our development server. After we worked with our DBA on refreshing our development environment, he indicated that one view was invalid in our development database (B384). He also noticed it was invalid on our production database as well. When I looked in the arschema table on the database to find out what the form name is, I could not find it. I can see Schema Ids from 1 through 630 with schema id 384 skipped. Based on the listing of forms (ordered by schemaid) I think schemaid 384 was a form that came with Change Management 5.6. Is there any other ways I can determine what schema 384 is or was? Does anyone have a list of all forms included with the Change Management 5.6 so that I can compare them to my listing of out of box forms? Thanks Peter Lammey ESPN MIT Technical Services & Applications Management 860-766-4761 __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
