Jim It all looks in order. However, can you check what the temp views look like at the R> prompt once created and send the definitions to the list? Perhaps we can spot something there.
"David Blocker [email protected] Office: 781-344-1920 Cell: 339-206-0261" -----Original Message----- From: Jim Belisle [mailto:[email protected]] Sent: Monday, December 7, 2009 10:41 AM To: 'RBASE-L Mailing List' Subject: [RBASE-L] - Re: I/O PROBLEMS WITH SIMPLE VIEWS Here is the code for UPDATING one viewform the other view: The views are created and I can manuallyedit data with no problem. CREATE TEMP VIEW View_OrdHead (Control#,ShipDate, FreightPro) + AS SELECT Control#, Shipdate,FreightPro + FROM OrderHeader WHERE Control# IN(&vControlList) CREATE TEMP VIEW View_BOLHead (Control#,ShipDate, FreightPro) + AS SELECT Control#, Shipdate,FreightPro + FROM BOLHeader WHERE Control# IN(&vControlList) -- Update OrderHeader, OrderShip &BOLHeader w/ Shipdates, FreightPros then delete nulls. UPDATE View_OrdHead SET FreightPro =T2.FreightPro FROM + View_OrdHead T1, View_BOLHead T2WHERE T1.ShipDate = T2.ShipDate AND + T1.Control# = T2.Control# This is where I get the I/O problem. Jim ------------------------------------------------------------ From: [email protected][mailto:[email protected]] On Behalf Of [email protected] Sent: Saturday, December 05, 20099:28 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: I/OPROBLEMS WITH SIMPLE VIEWS If a single-table view has an "order by", thatalso makes it not editable. I agree with others -- something in your view makes it not-editable. Maybe post your view syntax. Karen Jim, Just because a view is a single table view does not automatically make itupdateable. If for example it contains a GROUP BY statement then it is NOTupdateable. There are other syntax elements that might make a single table viewun-updateable.
