I don't get that error. I am on a windows box, but using an oracle db. I am also on 7.0.1 Patch 002. So it is either the version of Remedy, or the db. I would still put in a ticket on it. sounds like a bug to me.
Brian On Fri, Mar 28, 2008 at 4:11 PM, Elry <[EMAIL PROTECTED]> wrote: > Yes... > > It is a bit unusual, but we were able to replicate it in three > different environments. > > Try creating a field called "Function" to see if you guys can > replicate the error. > > If you can - then I think I will put in for an enhancement request. > > > > On Mar 28, 2:27 pm, Brian Goralczyk <[EMAIL PROTECTED]> wrote: > > Yea, I have never seen it on a field before. But at least it was an > easy > > fix. > > > > On Fri, Mar 28, 2008 at 1:22 PM, Grooms, Frederick W < > > > > > > > > [EMAIL PROTECTED]> wrote: > > > I have seen something like this before. All I had to do was just open > > > the form in the Admin tool and change the database name of the field. > > > When the Admin tool saved the form it created the view automatically. > > > > > Fred > > > > > -----Original Message----- > > > From: Action Request System discussion list(ARSList) > > > [mailto:[EMAIL PROTECTED] On Behalf Of Elry > > > Sent: Friday, March 28, 2008 12:10 PM > > > To: [EMAIL PROTECTED] > > > Subject: ARWARN 69: SQL view is not in place > > > > > Hi Folks: > > > > > (A) Environment: > > > Windows Server 2003 > > > MSSQL Database 2000 > > > ARS: 7.1.00 Build 200708221849 > > > > > (B) Error Message > > > "Creation of one of the SQL views for the form failed within the SQL > > > database. > > > Operation completed successfully, but the SQL view is not in place. > > > (ARWARN 69)." > > > > > (C) Root Cause: > > > Keyword "Function" not trapped. > > > Reserved Keywords: > > >http://msdn2.microsoft.com/en-us/library/aa238507(SQL.80).aspx > > > > > (D) SQL Profiler Create Statement (partial): > > > CREATE VIEW WLV > > > (Request_ID,Submitter,Create_Date,Assigned_To,Last_Modified_By, > > > Modified_Date,Status,Short_Description,Rollback_x) > > > > > Normally keywords are trapped and changed into something that won't > > > appear as a keyword: > > > i.e. "Rollback" as a field becomes "Rollback_x" > > > > > There may be other keywords that are not being trapped. The downside > to > > > this is that I did not see this prior to running a large amount of > > > workflow involving a form with this keyword. This resulted in my > > > spending 6 hours last night rebuilding the server. > > > > > Has anyone else had this experience? > > > > > > _______________________________________________________________________________ > > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > > Platinum Sponsor:www.rmsportal.comARSlist: "Where the Answers Are" > > > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > Platinum Sponsor:www.rmsportal.comARSlist: "Where the Answers Are" > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
