FireDAC.Phys.ADS.TFDPhysADSDriverLink.SearchPath

From RAD Studio API Documentation
Jump to: navigation, search

Delphi

property SearchPath: String read GetSearchPath write SetSearchPath stored IsSPS;

C++

__property System::UnicodeString SearchPath = {read=GetSearchPath, write=SetSearchPath, stored=IsSPS};

Properties

Type Visibility Source Unit Parent
property published
FireDAC.Phys.ADS.pas
FireDAC.Phys.ADS.hpp
FireDAC.Phys.ADS TFDPhysADSDriverLink

Description

Specifies the search path for free tables.

Use the SearchPath property to specify the search path for the free tables of the FireDAC Advantage driver.

If the opening table does not have a fully qualified path and the table is not found in the default path (see DefaultPath), then each directory in the search path is searched for the table.

For CREATE TABLE, the default path is used if it is supplied. Otherwise, the first search path is used.

For example, if there is no default path and the search path is f:\data; g:\data, then CREATE TABLE creates tables in f:\data .

When using a search path, the file is checked on the client so that it does not have to attempt to open the table on each server in the search path. If there is no search path, then the file is not checked on the client and the table is assumed to exist in the default path.

When using the Advantage Internet Server, the use of a search path can cause the Advantage driver to connect to each server in the search path because a connection is required before the check can be made.

For example, if the search path is \\server1\vol1\data; \\server2\vol1\data, then the Advantage driver connects to both server1 and server2 if a table exists on server2 and not on server1.

If this is not desired, then an application should avoid using search paths and either use the DefaultPath or supply a full path with each open or create request.

See Also