Insert Picture source file with IP address

[pugmuffin]

I would like to build a script that insert a picture into a container field and am unsure on how to specify the Source File in the "Insert Picture" step.

The source file exists and resides on a Windows which is accessible via a Mac client.

Every format option ( image:, imagemac: & imagewin: ) produces a "100" error.

The source file variable is in the format of "//198.16.0.211/INTERFACE/tn_f9ml130.jpg"

I'd appreciate any suggestions.

[IdealData]

You appear to have 2 leading slashes in your filespec. The FMP filespec is only 1 slash.

[IdealData]

WARNING

If you use the IP address of the picture server then you will always have to hold your picture on the same IP address (and path for that matter).

"Stores as reference" in an FMServer environment is very difficult to manage and maintain, just think your way down the line a little and you'll see where it will breakdown.

Look at holding your images in a separate table, or possibly file and make sure you store the images without reference.

[Fenton]

The original poster's IP address is an internally assigned IP address. So a new server could be assigned to that same IP address (though that could have repercussions on other uses). Wouldn't that work?

There is a 3rd alternative. Which is to combine the use of inserting/storing as a reference only, with a calculation field to produce and show the image. The path to the image file can be extracted from the "info" for the image, using GetAsText ( image ). You can then use the last part of the path (or however much you need), and combine it with a "constant"* IP address (or however much you need). So that you can change that first part later if needed.

*It would be a regular field in a "constants" 1-record table, not a global field.

There is no "perfect" solution to graphics, otherwise we'd all be using it. That's why there are so many posts about it. IdealData's is the simplest method in many ways. But it often depends on exactly how you're going to "use" the graphics as to which is the best method for you.

[pugmuffin]

Hi IdealData,

1) # of slashes

I'm using two slashes (//) because I'm trying to access a network share (Win 2003 server. But I've tried just about every combination.

2) Pictures at the same IP address

The pictures are managed by a MS SQL application. By connecting via ODBC to MS SQL, FileMaker figures out where the image is located. That logic works great. Pictures will always be at this IP.

3) Agree on "stores as reference" and managing. Images are going into a separate table. It works much easier that way.

Thanks IdealData, Its good to talk to someone about this.

Alan

[pugmuffin]

This is more background info...

The issue seems to be going more into "getting a OS X FileMaker to work in a Windows Active Directory Network"

I had a solution working fine on a Win XP system running FileMaker and accessing the Win 03 Server. But I'm now on a Mac (thankfully) and while I can access throughout our Windows network just fine... FileMaker is having difficulties finding the network path.

I've been working with our Net Admin and we are not having any success.

[pugmuffin]

Hi Fenton,

Regarding the "perfect" graphics solution, while its a little off topic to what I'm wrestling with, I've found what you and IdealData are discussing to be the most practical.

Our graphics are in such a state of flux where they can change. We use FM for reporting on the status of the graphics. Currently I just find what graphic has changed and refresh the FM version.

"Stores as reference" is something I will be exploring later, it was just so easy and relatively quick to just let FM refresh the images.

My original issue still seems to be between OS X, FM and a Windows server. My Mac OS ID & PW work fine with other Windows access and from what I see that is what FM uses to access the Windows network.