Thanks, Juan! According to my records and memory, the field has been named "User" for at least the past nine days. But I guess it is possible that I made some innocent change that I don't remember that triggered the problem.
The big question is, now that I have made the mistake, is there any way of reversing it other than by creating a whole new form, and repointing the workflow from the present to the new form? Dwayne ---- Original message ---- >Date: Wed, 20 May 2009 08:56:43 -0700 >From: Juan Ingles <juan.n...@gmail.com> >Subject: Re: Missing field’s ghost haunting form >To: arslist@ARSLIST.ORG > > ** Did the field ever exist? I'm guessing it failed > under the covers on creation when Remedy went to > actually create the table. The word "USER" is a > reserved word in the database. That's why the name > in the view has the "_X" tagged onto it. ( Same > reason the view for the user form is named "User_x" > ) > > It's best to stay away from reserved names, as all > sorts of weird things can happen as a result. > If you can, I would suggest recreating the form and > name the field something different. > > Juan Ingles > > On Wed, May 20, 2009 at 8:20 AM, Dwayne Martin > <marti...@jmu.edu> wrote: > > Dear List, > > I have a form (“PCS:Asset”) that had a field > called “User” that has mysteriously > disappeared. In sql, if I select all the field > IDs and names from the “field” table, it > isn’t there. > > But when I try to save an entry I get an error > saying “ARERR [552] Failure during SQL operation > to the database : ORA-00904: "USER_X": invalid > identifier.” > > The SQL log shows: > select …, USER_X, … from PCS_ASSET where > ASSETT_ID = 'PCA0000005' > . . . */*** ERROR *** ORA-00904: "USER_X": > invalid identifier > > So my field is gone, but its ghost remains in the > SQL view to haunt me. > > If I look for “Fields in View” the field > isn’t in the “In” or “Not In” table. > > I tried “DROP VIEW PCS_ASSET” and adding a new > field to see if Remedy would rebuild the SQL view, > but if I do “DESC PCS_ASSET” I see the new > field, along with “USER_X > > If I try to create a new field with the same name > and ID, it first complains that the “User” > name is already in use, then when I change the > name it says “Field does not exist on current > form : 565000229 (ARERR 314).” > > This problem may have something to do with the > “_X” after the fieldname. Maybe I put two > spaces after the name. > > I’m thinking of starting over from scratch. > Any other suggestions? > Dwayne Martin > James Madison University > (ARS 7.1 p3, RH Linux server, Oracle 10.2 db) > > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: > "Where the Answers Are"_
