Several CyberTracker features can be triggered via the command-line. This functionality is usually intended for server side scripts that operate on the database as a whole. To use the command line, use:
cd "\Program Files\CyberTracker Software\CyberTracker 3.0"
Note, do not use "ct3.exe /?", because this will trigger the windows application. Instead, just type "ct3".
"System" folders are mentioned below. These are sub-folders of "Documents\My CyberTracker Databases\System". This folder can be opened in Explorer to see the way data moves through the system.
Data that is waiting to be inserted into a database is placed into this folder. This folder is processed by CyberTracker routinely, e.g. on startup, on sync, etc. If the data cannot be uploaded into the target database for any reason, it will remain in this folder - potentially indefinitely.
Once data has been successfully added to a database, it is moved to this folder. If the database later becomes corrupt, it acts as a second line of defense.
If CyberTracker crashes, the changes that have been made since the last save are exported to a CTX file and placed here.
When files are downloaded from the internet, they are temporarily held in this location.
CyberTracker keeps a log of all sync operations. Check out the download.txt file in this location to understand errors. This only affects ActiveSync and Hotsync operations.
Virtual Earth tiles that are downloaded from the server are placed here to improve performance.
Once files have been downloaded via a local sync (ActiveSync or Hotsync), they may need to ultimately be sent to an internet server. Check out the "Send on Sync" option on the "Database Properties" dialog. This is a holding location for them before they are processed.
Local system settings, e.g. the current Client Profile.
Connect to the a Windows Mobile / PocketPC PDA and download any data that is on it. As soon as data is downloaded from the PDA, it is placed in the Staging (see above) folder.
Use the download settings of the associated /Database to connect to a URL. Incoming data is placed in the Staging (see above) folder. If an /ExportDatabase, /ExportRule and /ExportTable are also specified, then this downloaded data will be exported.
Process the Outgoing (see above) folder.
Specify a data file (.CTX) for use with data operations, for example as an input for the /ExportTable mechansim. If the full path is not present, the system will attempt to locate the file in "Documents\My CyberTracker Databases".
Specify the database to use for data operations, for example as an input for the /ExportTable mechanism.
The export rule file. The export rule file can be created by using the "Export View" toolbar button with the "Query Editor" active. Use the "Save as type" drop down on the File Save dialog to select "Export Rule File".
The target database for export operations. Must be accompanied by a /ExportRule and /ExportTable. The input for this operation comes from a /Datafile, /Database or /DownloadURL command. If the full path is not present, the system will attempt to locate the file in "Documents\My CyberTracker Databases".
The table name in the target database. This table must already exist and be properly configured. See "Using Export Data Tables" in CyberTracker Server Setup.
Turn on all CyberTracker features and run the desktop application.
ct3 /Database mydb.mdb /DownloadURL
Open the database mydb.mdb, get the download settings and execute a download using the parameters in the "Database Properties" dialog. This is equivalent to clicking the "Download" button on the "Database Properties" dialog box.
Download all data from the currently connected Windows Mobile device.
ct3 /Database myin.edb /DownloadUrl /ExportDatabase myout.edb /ExportRule myrule.exr /ExportTable mytable
Open the database myin.edb and get the download settings. Download all the files available using the parameters in the "Database Properties" dialog. Export this data to the myTable table in the myout.edb database. Note, myin.edb and myout.edb can be the same database.
Using this method is the preferred way of configuring a schedule task that keeps an export table up to date, because only the newly downloaded data is considered for export. More details on export tables can be found here.