I haven't run into this exactly, but I have run into a case where a view was manually created in the database and then a form with the same name was created and Remedy wasn't able to create the view. That caused some grief.
On Fri, Mar 28, 2008 at 12:09 PM, Elry <[EMAIL PROTECTED]> wrote: > 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 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"
