Thanks, Joe.  I looked thru the complete view list, and there are no views that 
remotely resemble "LA_SoftwareInstall"

The create statement in the sql log is too long to print here, so I'll 
summarize:

CREATE VIEW LA_SoftwareInstall (Install_number. . . [entire field list] . . .) 
AS SELECT T424.C1,C2,C3,C4,C5,C6,C7,C8,C536870913 . . . [more field names] . . 
.FROM T424, B424 WHERE T424.C1 = B424.C1,T424C536870999,T424C560000031 WHERE 
T424.C1 = T424C536870999.entryId AND T424.C1 = T424C560000031.entryId

Notice the two "WHERE"s.  If we drop the first "WHERE" clause and manually run:

. . .FROM T424, B424, T424C536870999, T424C560000031 WHERE  
T424.C1 = T424C536870999.entryId AND T424.C1 = T424C560000031.entryId

it creates the view.

So the question is, Why would Remedy throw in an extra WHERE clause and create 
an invalid sql statement?

Several people have suggested that the use of keywords as fieldnames might be 
causing the problem.  I think I've eliminated all such possibilities, but just 
in case somebody has time to look thru them all, I'll write the entire field 
list from the CREATE View statement.

Install_number,Submitter,Create_date,Assigned_to,Last_modified_by,Modified_date,Status,Software_title,First_name,Version,
Platform_DELETE,Valid_through,Attachment_Field,Vendor,Date2_requested,Server,College_Coordinator,General_Comments,Attachment_Field2,
Received_media_PC_,Received_license_,Last_name,Phone,Room,JMU_e_ID,A__Licenses__0_for_unlimited_,Date2_needed,Classes_using_software,
What_software_does,Distribution_Scripts_Before,Distribution_Scripts_After,Launch_Scripts_Before,Launch_Scripts_After,
Path_to_executable_file,Run_once_,System_Requirements,Command_Line_Parameters,Working_Directory,GUID,Reboot_,Associations,App_Launcher,
Start_Menu,Desktop,System_Tray,Source_Path,Target_Path,Application_Object_Name,File_Rights,Msc_Info,
Permissions,Read,Write,Create2,Erase,Modify2,Fire_Scan,Access_Control,Install_type_radio_box,Classification,Install_type,Group2_name,
Path,Received_Install_Instructions_,Catalog__,Purple,Action_requested,License_ID_PC,Why_on_Hold,Renewed,SoftTrack_id,Vendor_Web_Address,Vendor_Technical_Support__,Software_Name_and_Version,License_Info,Include_in_web_,Software_Type,Z_RequestID2,Z_RequestID3,
Renewal_changes,Send_Renewal_Notice,Renew_for_next_year,Temp_Char_Stored,Labs_currently_with_this_softw,Renewal_Diary,Current_month,
Z_Valid_through,Temp_char_display,Lab_list,Temp_char_db,Current_Year,First_round_deadline_date,Second_round_deadline_date,
First_email_date,License_ID_Mac,Platform,Department,Building,Department_purchased,Attachment_Field3,Temp_Character_Field,
Temp_Character_Field2,Temp_Character_Field3,Temp_Character_Field4,Temp_Character_Field5,Temp_Character_Field6
 

Dwayne Martin


---- Original message ----
>Date: Wed, 13 Feb 2008 23:35:51 -0500
>From: "Joe D'Souza" <[EMAIL PROTECTED]>  
>Subject: Re: Form sql view not found  
>To: arslist@ARSLIST.ORG
>
>I'm assuming you are on Oracle..
>
>Before modifying the table with that new field query the all_views table to
>see if there exists a view by the name 'ViewName_A'.
>
>Select view_name from all_views where view_name = 'ViewName_A'
>
>Replace ViewName with the actual name of the view while running that
>statement. If you find a view by that name, drop that view
>
>Drop view ViewName_A;
>Commit;
>
>If you are not on Oracle do the above equivalent for that DB..
>
>Then modify that form by creating the extra optional field.. The creation of
>the view failed probably because the ARS couldn't rename the existing view
>to ViewName_A because of an already existing view by that name..
>
>Joe
>
>-----Original Message-----
>From: Dwayne Martin [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, February 13, 2008 1:16 PM
>To: Joe DSouza
>Subject: Fwd: Re: Form sql view not found
>
>
>Joe,
>
>SORRY!  I was wrong.  Your rft file did display afterall.  It was just
>buried under a buncha other windows.
>
>As I noted in my reply to Fred, when I try that I get:
>
>"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)."
>
>
>Thanks,
>
>Dwayne
>
>No virus found in this outgoing message.
>Checked by AVG Free Edition. 
>Version: 7.5.516 / Virus Database: 269.20.4/1275 - Release Date: 2/12/2008
>3:20 PM
> 
>
>
>
>_______________________________________________________________________________
>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"

Reply via email to