Quote:


Table view is largely intended as a diagnostic and data repair facility (much as it was intended (and used) in Q&A). In that light, the data is shown with the least formatting and the actual field names are used. The idea being that nothing is disguised. You know precisely what you are editing and what the database engine believes its value to be. Furthermore, event programming is turned completely off - so that edits are not altered before being sent to the engine. It is really the only way in Sesame to get to the actual data as it appears on the engine, by the name the engine uses.

It may well be, that we'll introduce a second table view that is intended for data entry by end users, that formats values, that runs event programming, that uses LE names insteads of field names, supports non-mandatory restrictions, etc... But, as it stands, these features would each in their own way, obscure or interfere with table view's ability to operate as a low level access point to the actual data.

Because, table view does allow this kind of necessary access, you will note that the "data entry" user level is given only "read only" access to table view.

Quote:


Here, I agree entirely, the ability to copy and paste multiple rows would be a nice addition. It would also be nice to have a similar facility for forms as well. The Q&A model of "Dittoing" the last form viewed is too limited and imprecise. We've been looking for a good way to use the GUI model of Copy/Cut/Paste as applied to entire forms, but as you might imagine - that can be very complicated when dealing with subforms and a dozen or so "widget" types - some with multiple "views".

Just wanted to add some info on problems I am seeing in Sesame 1.0.3 that MAY be bugs.

1. randomly, while in preview or add/search mode, the close/open command view option brings the botton grey border up about 3 inches, thus hiding much of the form. Doesnt go back down unless I exit the form, then try again. I dont see a pattern here, its just random. My command buttons for "close/open command tree" does the same thing, randomly. Doesnt affect programming, but VERY annoying.

2. while trying to make default value of any tabpage to "not visible", the Property Viewer always shows Visible: True, although the tab page is actually not visible while in preview mode.

3. Possibly related to #2, programming crashes if tyring to make an invisible tab page to visibile [visibility(tabpage3,1) ]. Test Program does not find error, but preview aborts all programming.

Just wanted to throw this out on the table, in case you weren't aware.

Thanks again for all the support.

Steve in Texas

Erika,

I tried hiding one page at a time using the following programming:

visilibilty(tabpage1,0)
visibility(tabpage2,0)
visibility(tabpage3,0)

The propery viewer always said "visible:true", but when in preview, all 3 pages were successfully hidden.

I tried programming such as:

if StockNo = "large widget" then visibility(tabpage3,1)

and I think thats where I got the message "some programming didnt work, no event programming will run....".

Thanks for your help.

Steve

Well, it just seemed to make sense that this would work. I want different pages to show up depending upon the action selected.

However, I think Mark mentioned he is working on a fix that allows programming to "goto" a certain tab page, so this may be what Im after.

Also, what is the command for "hiding" or showing the "tabgroup"?

Thanks
Steve in Texas

Steve,

Are you using the most current version? We fixed a bug having to do with tab "artifacts" left behind, especially when using Undo in combination with Tab Page actions.

The "retaining current parent" message means that all of the currently selected elements cannot be moved onto the Tab, usually because they don't all fit. In that case, you need to move them on in smaller groups.

Im using 1.0.3.

Also, I made sure my tab page was Much much larger than needed to house the LE that I was moving. (I do this becuase the screen really jumps around when trying to drag an LE to an area just beyond the edge of the screen. Also frustrating, but my "Love" for Sesame has allowed me to persevere with this and other "annoyances".

Thanks again for hearing me out

Steve in Texas

ps. I dont use undelete, in general so I dont think my issues are related to this.

One more thing. Is there a chance an LE may have ''slipped" behind the canvas? If it did, it seems there would  be no way to recover it if it is near the top left of the form. Maybe a print of the form would reveal this?

I'm sure I started this app in ver 1.0.2. I'll send you the files.

Thanks!

Steve in Texas