Get physical location information for the local computer system.
Reference
Control Information
| Object Name |
WebLocationCtl.WebLocation |
| File Name |
CSWIPX12.OCX |
| Version |
12.0.3024.1286 |
| ProgID |
SocketTools.WebLocation.12 |
| ClassID |
A8E6A3FF-248A-420C-88A4-0453B1F270C1 |
| Threading Model |
Apartment |
| Help File |
CST12CTL.CHM |
| Dependencies |
None |
Overview
The Web Location control returns information about the location
associated with the with the external IP address of the local system.
The accuracy of this information can vary depending on the location,
with the most detailed information being available for North America.
The country and time zone information for all locations is generally
accurate. However, as the location information becomes more precise,
details such as city names, postal codes and specific geographic
locations (e.g.: longitude and latitude) may have reduced accuracy.
This location information should not be used by programs that
require extremely accurate map coordinates, such as navigation
applications. The location information in North America should be
generally accurate within a 25 mile (40km) radius. However, given
the nature of how IP address location works, there is no guarantee
that location information for any specific IP address or network
will be accurate.
Software that is designed to protect the privacy of users, such as
those which route all Internet traffic through proxy servers or VPNs,
can significantly impact the accuracy of this information. In this
case, the data returned by this control may reflect the location of
the network or proxy server, and not the location of the person using
your application. It is recommended that you always request permission
from the user before acquiring their location, have them confirm that
the location is correct and provide a mechanism for them to update
that information.
This control uses SocketTools services and will only
function if there is an active Internet connection and the local
system is capable of establishing a secure connection to the location
service.
Requirements
The SocketTools ActiveX Edition components are self-registering
controls that are compatible with any programming language that
supports the Component Object Model (COM) and the ActiveX control
specification. If you are using Visual Basic 6.0, Service Pack 6 (SP6)
is required. We recommend installing all available updates for your
development tools. Although the Visual Basic 6.0 runtime is supported
on Windows 11, the IDE itself is no longer officially supported by
Microsoft. Legacy IDEs and compilers may also require elevated
(administrator) privileges to run properly.
The ActiveX controls are supported on Windows 7, Windows Server
2008 R2, and later versions of both desktop and server editions of
Windows. For Windows 7, Service Pack 1 (SP1) is the minimum
requirement. For Windows 8 systems, the 8.1 update must be installed.
On ARM-based platforms, the minimum supported version is Windows 10
build 1709.
SocketTools includes components for both 32-bit (x86) and 64-bit
(x64) Windows platforms. All modern versions of Windows are 64-bit,
but we continue to include 32-bit components for compatibility with
legacy development tools such as Visual Basic 6.0. We also provide
native ARM64 ActiveX controls for systems running Windows on ARM. Note
that 32-bit applications on ARM run using x86 emulation, and Microsoft
no longer supports native ARM32 applications.
If you are using VBScript, Visual Basic for Applications (VBA), or
another scripting environment on an ARM-based system, be aware that
64-bit hosts will require ARM64 components, while 32-bit hosts will
use x86 components under emulation. This includes applications created
with Visual Basic 6.0. To reduce deployment complexity and avoid
confusion, SocketTools does not include ARM32 ActiveX controls in its
standard redistribution packages but they are available on request for
legacy or specialized scenarios.
Distribution
When you distribute an application that uses this control, you can
either install the file in the same folder as your application
executable or as a shared component in the appropriate system folder.
If you install the control in the system folder, it is important that
you distribute the correct version for the target platform and it
must be registered. If you install the control in the same folder as
your executable, it is recommended that you use registration-free
activation or COM redirection to ensure that the correct version of
the control is loaded by the application.
|