quote:
Originally posted by Andre DDB
It seems we are going OFFTOPIC [}:)].
Yeah. So what? [:D][:D][:D]
quote:
One of my main problems is to avoid unintentional changes of table data within the designer.
Yes, this is also one of my main concerns when zooming around in table data in the object designer [;)] So - why don’t you create two different user accounts, where one is assigned a role with no rights to change table data and only change objects, the other one with full permissions? For pure development, you can then log in with the “read-only” account. We actually have created a role of this kind - it contains the entry “Table Data”/0/Read=Yes and nothing else. It’s for users who perform reporting and analysis, but have no intention to change anything.