This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
By “results of a form,” do you mean something like data entered into the base by way of a form? If that’s what you mean, then I don’t know what to make of the second part of your request. First, views and tables are not alternatives to one another. Tables are accessed through views, and a form is one of the types of view (like grid, Kanban, calendar, gallery). So a form is always tied to a table. If the table is called BOOKS and you use a form to enter the name and other info about a book, the data goes into the BOOKS table. It doesn’t have to be displayed in the first view in the list of views for that table. You could filter that view to hide things in some way.
Now if for some reason you want to have two tables, like BooksIn vs BooksOut, well, you could use the form to get data into BooksIn, and then on some regular basis, copy records from that table over into BooksOut.
Make any sense at all? If not, please provide more details.
