your local file paths are NOT accessible via WAN or LAN. They may work if you connect via a browser on the server itself, but it will never get you what you want outside the machine for direct reference.
If you can calculate the path, then you should insert the images via script to a container so they will be accessible externally.
You can have a server scheduled script run with some sort of frequency if needed to update the images in your staff directory. Storing them in a filemaker container is the way to go though. Those are the best compatible and also get optimized for web transmission by the filemaker web publishing engine.
The problem is that I am using an ODBC data source (MS SQL) and that I can't directly store images in it. I thought about creating a path (Calculation result as a container : "image:drive/directory/file" & employeeID & ".jpg") and to refer dynamically to that path. I would only need to create images with the right name in the right directory.
Is that a possibility? Otherwise, I thought about doing a one to one relationship between two tables and use a table with only one field to store the image. My insert image script would create a new record in that table and link it with my main table.
The main thing here is that I CAN'T store a container in my table containing employee information.
make a 1:1 relationship to a filemaker table to store your images. If you're using SQL already you should have a valid unique ID for your table. The filemaker table can just be SQL ID and container, simple two fields.