Mat,
Did you check to see if you can run the same command in Query analyzer and see if it timesout there?

If it times out there maybe your server setting is timing you out not MM.
the Connection.Timeout feature is in the mmDataAccess object if i recall.
I think you have to override the facory object, and then add your settings to it.
I am doing this from memory, i will check later tonight in the help file and framework...i did see something like this but can't remember where.

HTH
--Shawn

>Shawn,
>
>Thank you for the reply, but I don't think this is the problem I am encountering. I had tried changing this in my app.config file, but it did not help. I could be wrong, but I don't think this setting applies to the individual queries. It looks like SqlCommand.CommandTimeout is the property I need to change, I am just not sure how.
>
>Kind Regards,
>
>Mat
>
>
>>Hi Mat,
>>
>>Right from the MM help file... :-)
>>
>>You can specify the timeout value of a SQL connection within the connection string. For example, you could put the following in your application configuration file:
>>

>><add key="maindata\Connection" value="server=(local);Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Northwind;Connection Timeout=30" />
>>

>>You can also access this setting by means of the ConnectionTimeout property of the connection object.
>>
>>--Shawn