Quote:Paul D & SRKTRY,
If I correctly understood SRKTRY's explanation of what it is that you want to accomplish, your answer is in Sesame 2.0, which was just released over the weekend at the Sesame Users Conference.
My understanding is that you want a Table View subform AND a Form View subform of the same records, so that you can select the records you want to work with in the Table View subform, then have the Form View subform display that same record in order to take advantage of the more advanced layout elements. This approach has problems, like the fact that the record will be locked in the Form View subform, because the Table View subform will already have been the first to open that record. (And there are other issues which I won't get into now.)
In any case, I believe you may want to use the new Table View of your primary form (which can be activated automatically by programming) to display the list of records in a spreadsheet-type view. From there, you can click on a record, and then have a custom Menu Bar item that you can select to take you to the Form View of that record. From there, you can have a Command Button located on the form that would take you back to the Table View, if you wanted.
Both version 1.x and 2.x have Form View and Table View, but the Table View has been completely redesigned for version 2. It now shows the data in Table View formatted exactly the same as you have designed it to look Form View. That includes fonts, font sizes, foreground and background colors, formatting and alignment. Table View now also doesn't need to show ALL the fields/elements that exist on the form, you can have any subset OR all of them displayed in the table -- it's up to you. You can even save many various table layouts in saved Table Specs.
Version 2.0 has an additional 200 new SBasic Programming Commands! Sesame has taken an incredible leap in what can now be done with it.
Thanks Carl... Paul & I were not aware of the restriction with displaying the same data in both Table View _and_ Form View simultaneously but what we'd like to achieve still fits perfectly within that restriction.
Previously I mentioned that we do not want users to edit records directly in the Table View, only in the Form View so...
Do you have any code suggestions that will allow us to read the records in, based on the filters that may restrict what records will be visible (and refresh if any data changes, including new records) and display only in a table view (note the reduction in capitalised words to denote that this is a view that looks like a table but it is NOT Sesame's Table View) and have a button next to each visible record (lets say the max number of records visible in the tabled view is set at 20 ?) and when the button next to the record to be edited in the table view is clicked, that is the data that presents itself in the active Form View ?
At no stage do we want the user to even think that they can edit data within a tabled view but we do want them to be able to select, from that tabled view which record to edit in the Form data showing in the lower left of the screen.
To summarise... I think we only need to have the records in the tabled view as a "Read Only" per se.
Pages: 1 2 [3] 4 
Send Topic 
Print
Table question. (Read 7362 times)
