Cure My fear of Table View?

[Wickerman]

Ever since FIlemaker modified the Table Views so that users could crwate new FIELDS "on the fly", I've been kind of terrified of them -- because every once in a while *I* click on the "+" button on accident and wind up with a new Field.  

 

Usually I try to craft List Views that fulfill my clients' needs, but they almost always want to be able to use Table view, so I think I should "get over it.

 

So, what is the best way to "Client-proof" the Table views from user errors?  Would it just be by using Privilege Sets that bar access to Layout View? (I assume that if you don't have Layout privileges, FMP won't let you create new Fields, right?)  Or is there an alternate technique, perhaps involving Custom Menus . . .?

 

I probably want to shut down all those "Add Leading Grand Summary" type options, I'd guess?

 

What are the other danger spots for allowing relatively unsophisticated Users access to Table view?   

[Rick Whitelaw]

Hmm . . . Does table view actually allow the creation of new fields or just the addition of fields that already exist? I never considered this. I'm on an iPad and don't have access to FM now.

[bruceR]

"Does table view actually allow the creation of new fields..."

Yes.

Table view also allows DELETING existing fields.

No; not just deleting them from the layout; deleting them completely from the table.

[Rick Whitelaw]

Perhaps I haven't informed myself properly, but this is a disaster waiting to happen. Why would FM allow creation and deletion of fields outside the "usual" process? Why is this possible in table view and not in other views? I'm not saying it should be.

[David Jondreau]

Keep in mind that only users with Full Access privileges can add or delete fields.

[LaRetta]

It bothers me as well. Of course we can (and should) have privileges in place which rules but it catches me all the time since I'm full access. It is another attempt to cater to the User and enforce the 'spreadsheetish' feel. It was a poor choice that one.

Correction ... Providing it wasn't the poor choice only not providing developer control at layout level.

[Vaughan]

I've never used table view except for "developer" layouts. Users only ever see form or list view layouts.