V
Vitalijus J. Karalius
To initiate synchronization over the Internet, a client computer must make
an HTTP connection to an Internet or intranet server.
When using the Access interface, the user is asked to choose the replica or
the internet server from a dropdown list - with the InternetAddress
presumably sourced from the MSysTranspAddress system table.
Upon choosing an HTTP connection from the dropdown list, the MDB is closed
and there is an attempt to establish the HTTP connection.
If the client is connected to the internet, inability to establish an HTTP
connection within 2 minutes (default) results in a "Failure to write an
internet handle" message. If the client is NOT connected to the internet,
the "Failure to write an internet handle" message occurs within a few
seconds. This is normal behavior.
However, even though the InternetAddress in the MSysTranspAddress system
table is identical, when Jet 4.0 SP-7 is installed via Windows 2000 SP-4,
attempts to establish an HTTP connection using some databases results in an
immediate "Invalid HTTP Address" error message after the MDB is closed. The
same database completes the HTTP connection normally when the client uses
Jet 4.0 SP-6. Other databases with the same InternetAddress in the
MSysTranspAddress system table are able to complete the HTTP connection
using BOTH clients.
Is this a problem with Jet 4.0 or with Access - or is there something in the
MDB causing the issue? Installing Jet 4 SP-8 does not affect this behavior.
Any thoughts/solutions would be sincerely appreciated.
TIA
an HTTP connection to an Internet or intranet server.
When using the Access interface, the user is asked to choose the replica or
the internet server from a dropdown list - with the InternetAddress
presumably sourced from the MSysTranspAddress system table.
Upon choosing an HTTP connection from the dropdown list, the MDB is closed
and there is an attempt to establish the HTTP connection.
If the client is connected to the internet, inability to establish an HTTP
connection within 2 minutes (default) results in a "Failure to write an
internet handle" message. If the client is NOT connected to the internet,
the "Failure to write an internet handle" message occurs within a few
seconds. This is normal behavior.
However, even though the InternetAddress in the MSysTranspAddress system
table is identical, when Jet 4.0 SP-7 is installed via Windows 2000 SP-4,
attempts to establish an HTTP connection using some databases results in an
immediate "Invalid HTTP Address" error message after the MDB is closed. The
same database completes the HTTP connection normally when the client uses
Jet 4.0 SP-6. Other databases with the same InternetAddress in the
MSysTranspAddress system table are able to complete the HTTP connection
using BOTH clients.
Is this a problem with Jet 4.0 or with Access - or is there something in the
MDB causing the issue? Installing Jet 4 SP-8 does not affect this behavior.
Any thoughts/solutions would be sincerely appreciated.
TIA