If a database does not have a default view specified (which is easily done), certain areas of functionality don't work as intended -- especially when it comes to document collection operations (e.g. code that generates doclinks).
A co-worker recently encountered a particularly nasty issue in which looping a document ...
Not a very original one, but it still bugs me why the first tab I get when the debugger stops somewhere is the Breakpoints tab. Pretty useless information, usually.
I'd like to vote for (many) more Designer options. One would be to be allowed to indicate the default tab ...
When creating a new View, you can choose one of which will be produced inheritance. Exactly the same wants and the Form / Subform, since we have a very long time to configure all options again:
I do not know how hard this is to create but what would be a timesaver for a lot of us is to create some default content for a rich text field in Designer and have it generated in the Notes client.
For example for new documents I would like to have a table ...