The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
| |
|
Re: Check if User is connected to the internet
Posted: 07 Dec 07 10:51 AM
|
I could say use a winapi to get it done.Then you'd need a wrapper for it and then distribute that wrapper to all slx clients which is messy(if you ask me)
Why dont you open a http request for a website you know and see the response code and response length and if GT 0 then be assured that you have a connection.
btw what are you doing after you check your connection? |
|
|
|
Re: Check if User is connected to the internet
Posted: 07 Dec 07 12:40 PM
|
I am calling a web service that returns a newly generated value to the client.
On further review I already have this code in place so I can leverage this:
if (oXMLDoc.parseError.errorCode <> 0) then
call msgbox (oXMLDoc.parseError.reason)
else
...
On a related note.. This service is going in place so that a duplicate number is never generated - both remote users and network users will use this service to get the number. I am trying to decide whether to update the main db when the number is generated in the web service, or pass the number back to the client that requested (could be remote - so that change would have to sync back to the main db - so another number may be generated in the mean time), or to update the main db with the web service and the remote when the data is passed back... any thoughts from the gallery? thanks |
|
|
|
Re: Check if User is connected to the internet
Posted: 07 Dec 07 3:20 PM
|
Not knowing all of the details of the process you are automating - but based on what you said I would have the webservice maintain the unique number. You said that both remote and network users are going to access this service so maintain the sequence at the one point (the web service).
Just my thoughts for what it's worth.
Ted |
|
|
|
Re: Check if User is connected to the internet
Posted: 07 Dec 07 4:14 PM
|
| Getting the generated number back to the remote in real time is part of the requirement, so if I don't update the remote I will have to give it to them in a message box or something that requires another step for the end user more code to maintain with some Dev trickery.. So, I guess my question at this point is: If I update both the main db and the remote who requested it at the same time, will I have problems with syncing? (of course, it's syncing.. hehehe). It is kind of like if a remote and network user update the same field at the same time, then sync the changes to each other.. |
|
|
|