ODBC data source types:\nIs a file data source (File DSN) restricted to a single local computer?

Introduction / Context:
ODBC supports multiple data source configurations: User DSN, System DSN, and File DSN. Each has different scoping and storage characteristics. This question checks if File DSNs are inherently local-only.

Given Data / Assumptions:

• User DSNs are stored per user on a machine.
• System DSNs are stored for all users on a machine.
• File DSNs are stored in .dsn files that contain connection information.

Concept / Approach:
A File DSN is defined by a text file (.dsn) that can be placed on a local disk or a shared location. Its portability allows multiple machines to reference the same file, enabling shared connection settings (subject to permissions and driver availability). By contrast, a System DSN is specifically local to one machine. Therefore, the statement that a File DSN is local to a single computer is incorrect.

Step-by-Step Solution:
Identify that File DSNs live in files, not solely in machine registries.Recognize that such files can reside on network shares and be reused.Conclude that File DSNs are not inherently “local only.”

Verification / Alternative check:
Creating a .dsn in a shared folder and using it from multiple clients demonstrates cross-machine use, provided the same driver is installed and network access is available.

Why Other Options Are Wrong:
Scoping does not change by operating system; mixing up System DSN (machine-local) with File DSN leads to the wrong conclusion.

Common Pitfalls:
Assuming portability equals universal success—differences in installed drivers or security can still prevent connections even with a shared File DSN.

Final Answer:
Incorrect