Results 1 to 3 of 3
  1. #1
    Join Date
    Mar 2006
    Posts
    53

    Unanswered: Strange remote connection problem

    Vendor app (written in VB '05) connects fine building screens that list data from only one record but blows up building 'list' screens that list multiple records. Really strange-it works fine when run locally on the server (Win2K3) and when run from one developer's machine (which has VS 2005 but not SQLExpress) but not from other developer's machines (which have both VS 2005 & SQLExpress) nor from a 'user' machine (which has neither). All have .Net Frameworks 2.0, the developer machines have SQL Management Studio & connect fine via that.

    Vendor, of course, says it's a configuration issue so not their problem. I'm trying to figure out what they could be doing differently when building a list screen & therefore why it would fail. Fact that it works locally suggests that the failure is in the remote connection-but fact that it connects on 'single record' screens says that remote connections work. So what would be different about a request to return multiple records and why would it work locally but not remotely?

    BTW, Surface Area Configuration Manager won't run-it reports 'localhost does not exist on the network or it cannot be configured remotely'. This is when running the Configuration tool directly on the server.

    Any ideas?
    Now back on Oracle. The more things change, the more they stay the same.

  2. #2
    Join Date
    Feb 2007
    Posts
    38
    Two things that you can check.
    1. Can other machines PING to the server? This is just to check whether it's a network issue or not.
    2. Since the vendor's app is written in VB5, they may have used the connection string using ADODB.Command object, and define the ActiveConnection. Then location of the recordset is defaulting to adUseServer. So find out the definition of ActiveConnection.CursorLocation with your vendor see if they specified to adUseClient.

  3. #3
    Join Date
    Mar 2006
    Posts
    53
    I *think* you're confusing VB5 with VB.Net 2005 (aka VB '05), but I'll check anyway. There are other, better, ways in VB05 but AFAIK it's still possible to use the ADODB.Command object-so maybe they are.

    Thanks. (And yes, the other machines can PING the server. The really mysterious thing here is that it's obviously getting to the database-that's how it builds the single-record screens.)
    Now back on Oracle. The more things change, the more they stay the same.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •