I can't agree with this. We've done this many times and a View Form behaves like any other Regular Form. If the underlying database object allows inserts and updates and you have a unique indentifier which can serve as request_id field everything is ok.
Here an excerpt out of the documentation When creating view forms, remember the following guidelines and limitations: The database table must reside on, or be accessible to, the database that AR System is using. NOTE For DB2 databases, you can connect only to database tables in the AR System database. The ARAdmin user must have read and write access privileges on the database table. The database table must have a column (field) that enforces non-null and unique values. This column acts as the Request ID. If the administrator chooses a column that is not unique or that allows nulls, data corruption might occur. The Request ID field must be an integer or character field with 6–15 characters. Otherwise, the Key field list is empty, and you cannot create the view form. A view form can be manipulated as a regular form type with these exceptions: You can add only Required and Optional fields that correspond to actual columns in the data source. You can add a Display Only field only when the column name does not correspond to a column in the data source. A view form cannot be used in join forms. After you attach an AR System field to a column in the database table, you cannot reattach the field to a different column, but you can change other field properties. Status history, diary, currency, and attachment fields are not supported on view forms. You cannot change the type of a text field or change the length of any field after initial creation. FTS operations are not available. Only the following data types are supported in view forms: DB2—varchar, varchar2, char, clob, integer, smallint, real, double SQL Server—char, varchar, tinyint, smallint, int, text, real, float, decimal Oracle®—varchar, varchar2, char, clob, number, float Informix—char, varchar, int8, smallint, integer, text, smallfloat, float, decimal Sybase—char, varchar, tinyint, smallint, int, text, real, float, decimal You cannot use a view form to access LOBs on a remote database. Long columns (that is, text or clob) must allow null values. Kind Regards Conny -----Ursprüngliche Nachricht----- Von: Action Request System discussion list(ARSList) [mailto:[email protected]] Im Auftrag von William Rentfrow Gesendet: Samstag, 13. Dezember 2008 05:30 An: [email protected] Betreff: Re: Form to access/edit data in another user's table Sure, but not with the inherent built-in save/modify functionality that exists in regular forms. Assuming you have the correct permissions set up in the database you can write workflow to do this all via SQL actions. So essentially you create a view form to display the data and buttons/dialog windows to gather changes and direct SQL actions to perform the updates. I've been there, done that - it's workable but if you are doing anything complicated it can be very time consuming. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Ravi Sent: Friday, December 12, 2008 2:35 PM To: [email protected] Subject: Form to access/edit data in another user's table Hi: is it possible to create a form based of another table which is not just a view form. I want to be able to change the data in that table from a remedy form. The table currently exists under a different user on the same database. Thanks Ravi ________________________________________________________________________ _______ 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"
