We continue to use MSAccess2002 Internet Synchronization with quite
mixed results. I wanted to share one interesting lesson learned.
Lesson Learned: Synchronization uses the wininet.dll. Open the
Internet Explorer, go to the File main menu, and select the Work
Offline option. Now try an internet synchronize (any method). The
result is:
Failure to write to an internet handle. Try the operation again.
You get this error regardless of the actual online state of the
machine. This can be very confusing especially on machines using
FireFox or some other browser (no clear indicator of online state).
For ****table computers which may or may not have an internet
connection, the user may start IE, inadvertently elect to work
offline, then not realize the state of the machine when they are
reconnected to the internet.
The solution we used was to call the Windows API to test and rest the
online state of wininet.dll before calling the .Synchronize function
in our synchronize form.
I don't know about the rest of you, but I am weary of trying to
understand the manifold failure modes and interdependencies of
the .Synchronize method (JRO or DAO). If anyone at MS is reading
this, would you PLEASE consider opening this enormous black box just
enough so it can be used reliably...
|
