asked on

FM - Calculated Path for Container Field?

I'm trying to write a calc for a container field so that whatever record I'm on the container will show the appropriate document. I put the filewin path, but it just produced an shortcut icon (instead of showing the document) and when I clicked on the icon, a dialog box came up saying I didn't have the correct file path (yet I've used this file path in other situations). See attached.

Also, dragging and dropping doesn't seem to be the answer because: 1) we will have over 700 records, and 2) when you do so, the pdf file shows nicely, but it doesn't give an option to store only a reference to the file. I tried right-clicking, but this doesn't provide an option to store a reference either. I've written calc paths for pictures, etc. in a web portal easily; what's the procedure for Container fields?

rvfowler2

ASKER

Adding image.
-Container.JPG

ASKER CERTIFIED SOLUTION

challengeday

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

challengeday

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rvfowler2

ASKER

I don't mind doing this to learn, but I don't want to do this 700 x 5 times (that's how many files we have to reference. I'd rather do it via a calc so they all populate automatically. I was able to do this with our pictures via a web portal.

SOLUTION

challengeday

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rvfowler2

ASKER

First, each file is generated by scanning it in as a pdf. Then what I propose is to give it a naming convention, including a folder path by property and then by unit code as you see below. I just used my calc in a web viewer that I use for images and it worked fine in a web viewer for a pdf file, so why do I even need a container field? The drag and drop of the latter is nice, but it seems to automatically store it in FM; it does not give you the option of storing it as a reference only. The following code worked fine in a web viewer. Why not just use this for the 5 most standard docs, and then use ChallengeDays idea of a document table pulled over in a portal for all other docs?

"file://R:/TNTINFO/" & Tenants::PropCode & Tenants::EntityNum & Tenants::BldingRNum & "/" & Tenants::PropCode & Tenants::UnitCode & "/" & Tenants::PropCode & Tenants::UnitCode & "_InsCert.pdf"

rvfowler2

ASKER

I still don't see the advantage of the container field, since it doesn't seem to take a script like a webviewer (when I use the same script I use for my webviewer in the autocalc of the container field, it just shows an icon and when I doubleclick on it, it says the path is wrong.). In contrast, the webviewer is showing my pdf docs just fine. The drag and drop of the container field is nice, but scripting is my first priority since we have 700 records x 5-10 docs each. Or, maybe use both solutions? Thanks.

rvfowler2

ASKER

Question not fully answered, but other valuable information received.