Let’s dissect the keyword into its core elements:
When combined, these elements create a seamless, scriptable, and highly organized work environment.
filedot could handle relative linking using . (current folder) and .. (parent folder).
Example: filedot .\work\data ..\ams\links\ folder_link.txt filedot folder link ams txt work
# Syntax: ACTION|SOURCE|LINK_NAME|OPTIONS
LINK|E:\Data\Reports|E:\Work\Reports_link|READONLY
UNLINK|E:\Work\Reports_link||
COPY|E:\Data\Templates|E:\Work\Templates_local|RECURSE
You could extend filedot to parse the first column and execute different operations (LINK, UNLINK, COPY). This turns your text file into a work order script.
Reads a .txt file where each line follows the format:
source_path|target_link_path Let’s dissect the keyword into its core elements:
Example ams_work.txt:
\\server\data\projectA|C:\AMS_Work\projectA_link
\\server\data\projectB|C:\AMS_Work\projectB_link
Then filedot folder link processes each line, creating folder links. When combined, these elements create a seamless, scriptable,
Windows (Command Prompt as Admin):
mklink /D "C:\Work\ProjectA\linked_data" "D:\MasterData\AMS_Input"
macOS / Linux:
ln -s /Volumes/AMS_Storage/current_job /home/user/work/folder_link
| Problem | Solution |
|---------|----------|
| filedot command not found | Write your own script as shown above or search for legacy filedot.exe in old backups. |
| "Access denied" on link creation | Run terminal as Administrator (Windows) or use sudo (Linux). |
| Symbolic link not showing in AMS | Ensure the AMS runs with permissions to follow symbolic links. Some older AMS don’t support them; use directory junctions (/J in Windows mklink). |
| Text file encoding issues | Save ams_work.txt as UTF-8 without BOM. |