Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Lotus Notes, is it a database too ? 1
- Thread starter molly
- Start date
-
1
- #2
It depends on what kind of work Notes and Access are being used for. Here's some information from a book that I bought when I had to learn Notes:
[tt]
Rather than storing small bits of discrete data, like records in the tables of a relational database, Notes databases store documents, bundles of semi-structured data. Those documents may be shared among a number of users.
The purpose and components of a Notes database are very different [from a relational database]. Whereas relational databases are built to summarize and perform calculations on a large number of distinct records and fields, Notes databases are better suited to searching, categorizing, and navigating through text content; thus, their constituent parts are very different. The components of a Notes database may be divided into documents and design elements. Design elements provide structure and automation. The provide forms to fill in; views and folders with which to organize documents for the user (and, at time, to aid automatic processes); navigators, outlines, and framesets to help users navigate through the data; and any number of places to put program code to automate operations and manipulate data.[/tt]
One of the examples in this book is a checkbook:
[tt]For example, a bank check provides you with spaces for the date, an amount, a payee, a note on what the check was for, and a signature. The check itself also provides your name and address, your account number, and a unique check number. A Notes form can likewise fill in automatically generated data such as the document creator's name or a list of times the document was modified...imagine a button that would automatically void a check, send the check off to the payee, or automatically schedule similar payments at a later date.[/tt]
So with the check book example, there would be a form (check) that is the default form for all check documents in the database. The form is the in the front end (UI in notes language) and the document itself is in the back end. You have to have a form to display a document. Each document in the backend contains "fields". In the checkbook example, the document fields would be payee, amount, note, check number. Each document has a unique ID. Documents can be responses to other documents so you can have a tree structure showing the original and any responses.
Notes is a very different mindset from relational databases and takes a little time to get used to. Notes is good for:
Workflow, text searching, discussions. It's set up to do both desktop and web applications. All the desktop applications are run from within the Notes Client.
There's a NotesDesigner (that's the IDE) forum here (Forum245) that you could look through to get some ideas of what it can do. I've also posted a few explanations of the UI/Backend setup that may help you understand how that all fits together.
PMonett is an MVP in that forum and is who I go to when I have questions...he's the master!! Be sure to read any of his posts to get a really good idea of the kinds of things that Notes can do.
HTH
All quoted text above from Notes & Domino R5 Developer's Guide to Building Applications by Matt Riggsby (Copyright 2001)
Leslie
In an open world there's no need for windows and gates
[tt]
Rather than storing small bits of discrete data, like records in the tables of a relational database, Notes databases store documents, bundles of semi-structured data. Those documents may be shared among a number of users.
The purpose and components of a Notes database are very different [from a relational database]. Whereas relational databases are built to summarize and perform calculations on a large number of distinct records and fields, Notes databases are better suited to searching, categorizing, and navigating through text content; thus, their constituent parts are very different. The components of a Notes database may be divided into documents and design elements. Design elements provide structure and automation. The provide forms to fill in; views and folders with which to organize documents for the user (and, at time, to aid automatic processes); navigators, outlines, and framesets to help users navigate through the data; and any number of places to put program code to automate operations and manipulate data.[/tt]
One of the examples in this book is a checkbook:
[tt]For example, a bank check provides you with spaces for the date, an amount, a payee, a note on what the check was for, and a signature. The check itself also provides your name and address, your account number, and a unique check number. A Notes form can likewise fill in automatically generated data such as the document creator's name or a list of times the document was modified...imagine a button that would automatically void a check, send the check off to the payee, or automatically schedule similar payments at a later date.[/tt]
So with the check book example, there would be a form (check) that is the default form for all check documents in the database. The form is the in the front end (UI in notes language) and the document itself is in the back end. You have to have a form to display a document. Each document in the backend contains "fields". In the checkbook example, the document fields would be payee, amount, note, check number. Each document has a unique ID. Documents can be responses to other documents so you can have a tree structure showing the original and any responses.
Notes is a very different mindset from relational databases and takes a little time to get used to. Notes is good for:
Workflow, text searching, discussions. It's set up to do both desktop and web applications. All the desktop applications are run from within the Notes Client.
There's a NotesDesigner (that's the IDE) forum here (Forum245) that you could look through to get some ideas of what it can do. I've also posted a few explanations of the UI/Backend setup that may help you understand how that all fits together.
PMonett is an MVP in that forum and is who I go to when I have questions...he's the master!! Be sure to read any of his posts to get a really good idea of the kinds of things that Notes can do.
HTH
All quoted text above from Notes & Domino R5 Developer's Guide to Building Applications by Matt Riggsby (Copyright 2001)
Leslie
In an open world there's no need for windows and gates
- Thread starter
- #3
- Status
Similar threads
- Locked
- Question
- Locked
- Question