Hi, I wasn't on this list when this thread appeared and ended, but it appears to be precisely the topic that I was going to raise. As such, I wonder if I can add my vote for an RFE on this.
I've read in this previous message on this topic: http://dba.openoffice.org/servlets/ReadMsg?list=users&msgId=2384673 the reason that OOo doesn't allow updates from table controls (unless I've misconstrued). I understand the reason given: to prevent 'Joe' from unwittingly messing up his database, and that this is a conservative design choice. There was another thread where the poster was able to resolve the problem with a workaround for his particular needs. Like that person, I looked into the possibility of adding an index field to trick OOo, and other workarounds, without success. My problem is: I currently have a form that is bound to a PostgreSQL view and that contains a table control. I don't seem to be able to rework it to use a SQL query in place of a view such that editing is possible. It's a subform with link fields, and the view is an combination of two tables. I want to be able to modify data in some of the fields. PostgreSQL allows me to create 'rules' that intercept any insert, update, and delete actions on this view and via these rules I can correctly update the 'real' underlying tables. I imagine other DBMSs are similar. My 'Joe' is a Stream Morphology scientist that will be using the form but not modifying it. I want him to see the information that interests him in a format that is natural for him to work with. For example, I have a real table TaxaCounts that contains a key code (TaxaCode). I want Joe and others to be able to edit fields such as Count, QA, Comments in this table. I don't want TaxaCode to appear in the table control. Instead, I want Joe to see (but not edit) the Class, Order, Family, Genus, and Species names that the view extracts via TaxaCode from a second table Taxa. I don't mind the current restriction being a default, but I would like a way to turn the restriction off (e.g. an expert mode), possibly on a form by form basis. Just thought another actual case might help the discussion. Is it time to put that RFE in? Regards. Ross --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
