>>>Personally, I find a single connection held for the duration of the >>>application session much easier to administer than multiple connections >>>and this approach has never given me any problems to date. >>Something to bear in mind is your licencing agreement: if you are >>on 'Per Server' licencing, every open connection uses a SQL Server >>licence, even if they all come from one workstation. Additionally, certain programmers adhere to the philosophy to only keep open a table for as long as you need it. This especially helps to cut down on overhead (both the local pc and the server (Novell, NT, UNIX) and also cuts down on table corruption. Try doing this experiment: Backup the remote server's database and table (choose a small one). Open a connection. Turn the computer off. Look at some of the system screens in Novell, NT, or AS400. You will find the table still open, the user still logged-in. After a period of time, the user will most probably removed from the system due to inactivity (depending on your server's settings). But you'll find the table doesn't always close but has to be closed by the system admin. Gene Berger The Corner Analyst 13995 Graham Road Pataskala, Ohio 43062 (614) 927-8994 gberger@asacomp.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Displayed using 100% recycled electrons.