>>No. Which may be the flaw in my argument :-{
>>
>>I was just going to try it though. It seems as if pooling may not be enabled by default though it can be set in the data connection wizard or by adding 'OLE DB Services=-1' to the connection string. But that begs the question of why pooling is *not* the default....
>
>It *does* seem strange that it's not the default ... I wonder what is the reasoning behind that?

Never really used Access so I'm just guessing, but I don't think JET was ever intended to properly support multiple access (using it as a data store for a web app could get nasty quite quickly :-} ) so, if you are not doing that, one of the primary benefit of connection pooling disappears. But if that takes away one of the upsides of pooling it doesn't mean there is a downside to enabling it.
Maybe it's just a legacy thing - I've a feeling earlier versions may not have supported pooling so changing the default later would have been dangerous ?

Dunno really........