Well thanks for the response but I did not see any actual netserverenumerate function in that example ,
When examined, its a great set of functions which do a variety of other things that could be useful later, but doesn't appear that OdbcAPI set of functions can do any assessment of the network or browse other computers to determine if they are running MS SQL Server instances or not.
In the usage intended:
1) There are no data sources defined yet therefore listing datasources is not enough
2) There is always a SQL Server instance because if there was none, the process intended should not continue because the prerequisite steps were not followed or completed properly
3) The solution needs to be as dependable as possible in the detection of only MS SQL Server instances, but its not the only option because if the user knew the NETBIOS or IP address for the SQL server they could key it directly into a sle control and click connect/verify and the app would just go out and verify that a transaction object could contact that server but the point of this exercise was 'discovery' to help those less fortunate and to try and be kind and populate a drop down for the users directly more of as a courtesy.
Solution that seems promising:
Build a small c# .net core based dll in snapdevelop and using PB 2021 .net import routine imported it into PB and instantiated the nvo it generated, the c# sql location routine appears to be working reliably so in my opinion this task is now complete, on the surface this appears viable.
It does find my primary SQL sever so I will have to see if it can find SQL Express engines running.
Honestly, to my mind its a bit rough, would have preferred to be able to have all the functionality in PB but I just couldn't get the netserverenumerate function to work properly within pb, at least not on my windows 10 machines, something might have changed or such that would have to be addressed before it works like it should, or i just got some function declarations wrong or whatever, ...
Joseph
