We are using ListServ 1.8d on an NT platform (Version 4, SP 5). Our DBMS is MSSQL Server 7 on NT, version 4 SP 5. We have developed a web application (using ASP scripts ) that will permit our Customers to Opt-in or out for various electronic notifications. We have created the database and setup the tables to hold the Subscriber and List information. We are using an intersection table to relate Subscriber's to Lists. Each List record also contains a field that will hold the ListServ List name. I have reviewed the Developers Guide for ListServ, the List Owner's Manual for ListServ and the Site Manager's Operation Manual. In addition we received a text document that provided a quick Overview of ListServ and Dbms. My understanding is that either ListServ will require one big table (essentially a flat table or tables if a table is created for each list), or if we use our DBMS, then we can only distribute the lists via a one-time mailing mode. Under that constraint, our lists would not exist. I have experimented using views and editing the list header to use that view. This appears to work, however, the creation of new lists would pose a problem as ListServ will create a table. And the creation of new lists requires that the administrators access the ListServ Interface separately. A view can be developed for the subscriber table with the required elements for ListServ. However, appending the List Names as columns (in place of rows) was not possible in the view. We need to provide one interface for our administrators to manage subscriber information, lists, and the additional information maintained in our database. We need to minimize the amount of redundant data that is stored (that is why I was considering views). Has anyone successfully managed to integrate ListServ into their own application so that the entire process is seamless? Thanks, Angela Larson Web Designer/Developer