Why should it be reduced? Most databases work in this way; you deleted items in the database, you didn't make the database smaller. Any deleted items aren't "physically" removed, they're just marked as being "non-existent". Imagine a database having to remove a single string from 5 trillion others, and save a concatenated form back again. Databases are fast by doing things efficiently. No real "removals", but "marks". If you want to reclaim the space, you'll have to "shrink" your database. Access has it's way, as mentioned, and Sql Server has some sprocs. Bastard Programmer from Hell :suss:

There are many versions, for modest projects I prefer SQL Server 2008R2 Express Edition, here[^]. For others, search the Microsoft site, or google. :) Luc Pattyn [My Articles] Nil Volentibus Arduum

Mycroft Holmes wrote: and needs to cope with a long running stored procedure. And changing the connection timeout is going to impact that?

1. Assuming you only want to know about the rows affected using cn as new sqlconnection("ConnectionStringHERE") dim cmd as new sqlcommand cmd.connection = cn cmd.commandType = StoredProc cmd.commandText = "MyStoredProc" dim Results as integer = cmd.executenonQuery end using I would also look up SQLParameters and SQLDataAdapters Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch

This CP Article[^] may also help. ------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave CCC Link[^] Trolls[^]

ASP.NET for Dummies[^]. "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me

Maybe this will help. http://msdn.microsoft.com/en-us/beginner/bb308760.aspx Frazzle the name say's it all