> At first look, i would say that the connection-pooling of .NET Provider
> is enabled (by default). Therefore, the .Close() command does not really
> disconnect from the file. It just put the opened connection back to the
> pool. Try to add
>
> cs.Pooling = false;
>
>
> to your Connection-String.
> Be aware: connection pooling is not a bad thing for a production system.
> But it's maybe the problem in your test.

Brilliant! That was the solution to the problem. Setting pooling to false enables the file to be modified immediately after the connection is closed.

Thanks you so much!