Recent content by JohnPapa

  1. J

    Cannot connect to SQL Server on a network

    The problem was resolved for the Desktop-Laptop network. Unfortunately I still have the problem with the pc running W10 A365 32bit on the 4pc network. I will try to run the code step by step after I double check the firewall rules and the TCP-IP connectivity.
  2. J

    Cannot connect to SQL Server on a network

    Found the problem. In #18 above I said I use the following connection string from the desktop success fully ODBC;PROVIDER=MSDASQL;DRIVER=ODBC Driver 17 for SQL Server;SERVER=DESKTOP-KQTNJ42\SQLEXPRESS;UID=savf;Trusted_Connection=No;APP=Microsoft Office;DATABASE=VF3;PWD=1234 I use the same...
  3. J

    Cannot connect to SQL Server on a network

    The machine name is DESKTOP-KQTNJ42 and the server name is SQLEXPRESS
  4. J

    Cannot connect to SQL Server on a network

    Once I locate the "meat" I will send it over in a screenshot. SQL Server Browser was not running and it is running now. From both pcs I can enter the db through SSMS by using the following. I have made sure that both are looking at the same db, by making a change in one of the fields.
  5. J

    Cannot connect to SQL Server on a network

    The correct ODBC driver (bitnesswise) had been installed
  6. J

    Cannot connect to SQL Server on a network

    I have created a 2 pc network with a desktop and a laptop. The desktop runs W10 32-bit A365 and is called DESKTOP-KQTNJ42 The laptop runs W1112341234sa1234savf 64-bit A365 and is called JohnP The SQl Server is on the desktop and I can log onto SSMS on both with Server = DESKTOP-KQTNJ42...
  7. J

    Cannot connect to SQL Server on a network

    Will do thanks.
  8. J

    Cannot connect to SQL Server on a network

    I also found a suggestion of enabling Named Pipes.
  9. J

    Cannot connect to SQL Server on a network

    Just a clarification "DESKTOP-KQTNJ42" is the name of my pc, which is not on the client's Network The Network has 4 pcs called 1) Server 2) pc1 3) pc2 4) pc3 The problem is with pc2 with runs Windows 10. The other 3 pcs run Windows 11. The Network section of pc2 is indicated below and does...
  10. J

    Cannot connect to SQL Server on a network

    I have a meeting onsite shortly (on a Saturday). The W10 pc can see the Server (which is just a pc). I was able to create a mapped drive to the Server and SSMS can see the DB (VF3) which resides in the SQL Server on the Server. We have checked the firewall rules and will check them again.
  11. J

    Virus Trojan.Valyria.4814

    As I mentioned the specific problem has been reported by Bitdefender as far back as 2010. A good indication of a false positive is the fact in VirusTotal no AV flags it, including Bitdefender.
  12. J

    Cannot connect to SQL Server on a network

    At present we have a network with 4 pcs. The 3 run Windows 11 and they run ok. The 4th pc runs Windows 10 and cannot connect to the SQL Express All 4 pcs use: ODBC;PROVIDER=MSDASQL;DRIVER=ODBC Driver 17 for SQL...
  13. J

    Can Access 365 and Access 2013 coexist?

    Can Access 365 and Access 2013 coexist and I am not referring to the Access 2013 Runtime. Can these two versions of Access exist and can development take place in both these versions on the same pc?
  14. J

    Virus Trojan.Valyria.4814

    The problem resurfaced and I checked the specific quarantined files at VirusTotal, where Bitdefender did not flag it as as virus. As mentioned by Edgar in #4, it must be a false positive, so I added the specific folder in the Bitdefender exceptions.
  15. J

    Virus Trojan.Valyria.4814

    I do not know for sure whether Bitdefender is overly sensitive in a good or bad way or whether I checked the correct file on Virus Total. After running a complete system check in Bitdefender for the 3rd time it said it identified the specific virus and fixed the problem. From my research on the...
Top Bottom