On Sun, 24 Feb 2008 17:09:19 -0500 Drew Jensen <[EMAIL PROTECTED]> dijo:
> John Jason Jordan wrote: > > On Sun, 24 Feb 2008 15:35:22 -0500 > > > > Is there a way to allow Writer only to have read permission? > > > Well - yes, make a read only result set. Using any version of Base you > can create a VIEW from your query and this will always be a read only > result set. The down side for versions prior to 2.4 is that VIEWS can > not be edited, only created and deleted. Starting with 2.4 however you > you can edit them. > > So from the main Base window switch to your Query view. Highlight the > query and right click for the context menu, select 'Create View' and > save it. In the Beamer window of Writer select the VIEW instead of the > query - there is no way you can alter or delete the data at at this point. > > > When you go to use the query again, but with a new criteria string you > will need to either delete the views before you use it again, or create > the new view with a different name. > > Views are listed with the Tables in the Base window and the Beamer > window by the way - but have a slightly different icon. Something strange (but good) happened, which gives me yet one more question. After my last message I went to the store. On the way it dawned on me that I had made a copy of MainBank previously, right in the same database. So when I got home I made a query and, sure enough, the deleted records were still in the copy of MainBank. I was in the process of trying to figure out how to do an APPEND or INSERT INTO when the whole thing seemed to lock up. System Monitor said that soffice.bin was taking 45-50% CPU which, considering that I have a dual core CPU, means that it was sucking up nearly 100% of one of them. So I let it sit for 20 minutes or so, but there was no change, so I killed it. When I relaunched Base it came up with the rcovery window. It successfully recovered the database without incident. However, the queries that I had created were gone. MainBank and its copy were there. So I recreated the queries (copying and pasting your SQL as before). There are three exams, so I created one and then copied and pasted it a couple times to create the other two. And then for the other two I went into the SQL and just changed "LFa" to "LFb" and "LFc." And then I tested each one. Well guess what? All three worked perfectly, including the one whose records had been deleted. I opened MainBank and verified that the records were still there. Yet previously they were definitely gone. Conclusion: Base is not saving changes to a table until some event happens. While it saved me a lot of work this time, this is new to me and I need to understand how Base works here. Previously with Access, and recently with Kexi, when you change a record the change is written to disk the minute you move off the record. Evidently Base doesn't do things that way. At what point does Base write changes to disk? Should I save periodically as I do when working on a Writer document? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
