> We have developed an app with VB 16bit and connect through ODBC to MS
> SQL server.
> Everything works fine in our office under both development mode and
> run-time. However after installed at the client's site with almost
> exactly the same sw and hw configuration, we get the following error
> messages from time to time but inconsistent, meaning that we are not
> able to reproduce the errors:
> dbnmpntw write() connection fail
> sometimes they even encounter a connection fail when trying to log on.
> The sql server currently is completely dedicated to this project. Can
> anyone shed some light on this issue?
are you using IPX as the transport? i think that i have found a bug in the odbc driver
when using it. we have users that can manually attach to sql server (6.0) tables from
access(95), yet can only open tables that are about 50 rows or less. in addtion, these
same users can log in to the sqlserver using an app written in acces (7), yet after
the inital transaction are dropped from the server. this does not happen to all
users, and all hardware and software is EXACTLY the same (we have even gone so far as
to replace entire registries with those from working stations to test configuratinal
parameters). i am looking into other protocols to see if it is indeed specific to
i was told the reducing the packet size to 512 bytes may have an affect on this, but
it did not for us (i am a little suspicious if this is the problem unless you have a
network that is routed).
if you hear anything of interest, please pass it on.