Home > Tools User's Guide > Conduits
Appendices
Tags
The value of conduit parameters such as path or file names can contain special tags. These tags will be replaced during the execution of the conduit by the appropriate values.
| Tag | Value |
| {user} | Path to the home directory of the user who is currently performing the synchronization (eg C:\Palm\Bob\) |
| {username} | Name of the user who is currently performing the synchronization (eg Bob) |
| {windows} | Path to the Windows® directory. |
| {system} | Path to Windows® system directory. |
| {hotsync} | Path to the directory in which HotSync® is installed (eg C:\Palm\). |
| {HKEY_[CLASSES_ROOT | CURRENT_CONFIG | CURRENT_USER | LOCAL_MACHINE | USERS]\path\key} | Value of the registry key whose path and name has been specified. In case the key is not found, this tag is simply removed. |
| {appdata} | The file system directory that serves as a common repository for application-specific data. A typical path is C:\Documents and Settings\username\Application Data. |
| {common_appdata} | The file system directory containing application data for all users. A typical path is C:\Documents and Settings\All Users\Application Data. |
| {common_documents} | The file system directory that contains documents that are common to all users. A typical paths is C:\Documents and Settings\All Users\Documents. Valid for Windows NT systems and Microsoft Windows® 95 and Windows 98 systems with Shfolder.dll installed. |
| {local_appdata} | The file system directory that serves as a data repository for local (nonroaming) applications. A typical path is C:\Documents and Settings\username\Local Settings\Application Data. |
| {documents} | The file system directory used to physically store a user's common repository of documents. A typical path is C:\Documents and Settings\username\My Documents. |
| {program_files} | The Program Files folder. A typical path is C:\Program Files. |
If the tag cannot be replaced by its value, for example because it refers to a registry key that does not exist or to a standard folder that is meaningless on the system the conduit is running on, the tag is simply removed.
Examples of connection strings
Access 97 (will create 97 bases):
Provider=Microsoft.Jet.OLEDB.3.51;Data Source=PathToMyMdbFile;
Access, any version >= 2000 (will create 2000 bases):
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=PathToMyMdbFile;
SQL Server
Driver={SQL Server}; Server=mySQLserverName; Database=myBase; Uid=myUserName;Pwd=myPassword;DataSource=myComputerNameHeredBase
Driver={Microsoft dBase Driver (*.dbf)};DriverId=533;DefaultDir=myPathToMyBase;FIL=dBase 5.0;MaxBufferSize=2048;PageTimeout=600;Nota: the connection string can contain one of the special tags mentioned aboved. For example, you can use the string Provider=Microsoft.Jet.OLEDB.3.51;Data Source={user}\addresses.mdb; to use a distinct access 97 database file in every HotSync® users' directories. Whenever a path is specified in a connection string, it is created if it does not exist.