I already answered this in the microsoft.public.dotnet.framework.adonet
NG -- so please be kind and watch those multiposts. Someone else also
answered you threre. Anywhere, here's my answer (although please answer
over there)
You shoud close the connection as soon as you are done with it. If you are
performing an update with a DataAdapter, it opens and closes the connection
for you unless you tell it not to. This is the default behavior, and
particularly with Access, it's a good choice. I haven't seen this behavior
that you are speaking of, updates I send always appear to be effective
immediately, so i'm wondering how you are determining this? To that end,
I've used SQL server and Oracle exclusively, but I doubt there's any
difference b/c there's nothing that happens after a connection closes that
could cause this to the best of my knowledge.
--
W.G. Ryan MVP Windows - Embedded
http://forums.devbuzz.com http://www.knowdotnet.com/dataaccess.html http://www.msmvps.com/williamryan/
"cybertof" <cy****************@gmx.net> wrote in message
news:MP************************@msnews.microsoft.c om...
Hello,
When calling the .Update() method on a dataset to make the changes on
the undercover database (access .mdb), the changes are not reflected
immediatly.
If i close the connection, it makes the changes more quickly effective.
Do you have an idea how to force the update (writing the cache on the
disk) without closing the connection ?
Regards,
Cybertof.
