I know its basic but can explain DECs and where I can find it. Also isn’t it possible to do what DECs can by using ODBC and LSDO?
Is it also true that this overlaps what LEI can do?
Where does DCR fit into all of this?
Confused and need help!
My problem is that I need to work with a SQL database.
Thanks
Subject: Explanation of LEI, DECs and LSDO
I know its basic but can explain DECs and where I can find it.
Refer to www.lotus.com/ei for a description of the EI priduct offerings and how to obtain them – also note there is an Enterprise Integration forum here.
DECS comes with the Domino server.
Also isn’t it possible to do what DECs can by using ODBC and LSDO?
No – DECS lets the Domino server fetch fields from a relational database automatically, whenever a Notes document is used, without having to write code. Since the database operations happen on the server, only the server has to be configured to access the database. The database username and password can be kept private.
LS:DO does not support supplying field values whenever a document is used; e.g. during replication, when an agent accesses the document – but only when a form is opened on screen. You do have to write code, and the code executes on the user’s Notes workstation, so every workstation has to be configured with access to the database. The code will need to know the database username and password, so you have to take steps to prevent the user debugging your code and finding out what these are.
Is it also true that this overlaps what LEI can do?
DECS contains a small subset of the LEI functionality.
Where does DCR fit into all of this?
DCRs let you configure DECS functionality directly from Domino Designer. You can’t do any more with DCRs than you can with DECS. There are some things you can do with DECS that you can’t do with DCRs.
My problem is that I need to work with a SQL database.
We feel for you. 
Subject: RE: Explanation of LEI, DECs and LSDO
Thanks - very interesting. I guess my idea would be just to write the front end in ASP. I wonder, rather than having data in two places - notes and SQL, why not just use domino as the front end and access the SQL through a browser using Domino? This is a route I am going down so am yet to see if this will work.
I am going to use Domino to access the stored procedures in the SQL database so will be able to read, update, create and delete in the SQL DB.
I thought why bother having notes documents.
Can you see any problem to doing this?
Thanks
Subject: RE: Explanation of LEI, DECs and LSDO
You could get around storing any information in Notes documents by using a LEI Virtual Document. This requires either extra fields in your table or an extra table to store the header information that makes the relational record look like a Notes document (last modified date/time, “$” fields, and so on).
Alternately, you could, as you say, use an ASP, though in that case I’m not sure why you need Domino. The idea is to use Domino Designer to create the UI, a relational database to store the data, LEI to tie them together, and then you don’t have to write a lot of code to read the relational database and format the results.