Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 7052 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I have set up a container field in my database and store .jpg pics of clients in this field. I am using fmp 5.5 on a windows system. The files are on the server in a shared enviroment. I store all the files on the shared drive on the server with "Store only a reference to this file". Sometimes the picture shows up and sometimes I get the above error message. Also, teammember A can add the file and then no other teammember can view the file.

I'm sure this is a simple solution that has been addressed many times before, but I haven't run across the answer yet.

Anyone out there that can help?

Thanks

Posted

I have set up a container field in my database and store .jpg pics of clients in this field. I am using fmp 5.5 on a windows system. The files are on the server in a shared enviroment. I store all the files on the shared drive on the server with "Store only a reference to this file". Sometimes the picture shows up and sometimes I get the above error message. Also, teammember A can add the file and then no other teammember can view the file.

I'm sure this is a simple solution that has been addressed many times before, but I haven't run across the answer yet.

Anyone out there that can help?

Thanks

It's been several days and no posts. Does this mean there isn't an answer? Will someone please help?

Thank you for your assistance.

Posted

Hi Tammy,

I assume you've established that the folder is correctly shared and that all users can view the folder in their network neighborhood ?

Could it be that User A is actually working on the server and, when importing the picture, selects it from the local drive (e.g. D:/PathToPicture/Picture.jpg) in stead of selecting it through the network neighborhood. I've seen this happen in our own database and then you'll get the a.m. error message, because FM stores the local path and not the network path. Then, when the other users try to access it, FM will search for D:/PathToPicture/Picture.jpg, which of course isn't there.

When you import the picture, do you also import the pathname to a field ? This could be very useful troubleshooting the problem, i.e. to establish if there is a significant difference between the pathnames of the files that do show and those that don't.

HTH,

Peter

  • Newbies
Posted

Tammy,

We are trying to create a networked photo database and are having the same problem. We've got a Filemaker server computer, then we've got a Mac office server, where the photos are residing on a shared drive.

Our problem resembles yours, but is also a little different. Basically, one computer may react differently to different users. User A may log-in and be able to "see" the referenced picture files. User B may log in and not be able to see anything.

Have you clicked on the thumbnail view screen yet? The strange thing is that when we click on this, we can see all the pics, so FM must know where they are, right?

Any help or assistance with this would be greatly appreciated. We're having an IT volunteer come in today to look at our situation, so if he has any insight/solutions, I'll be sure to post and let you know.

Good luck

nadia

Posted

Have you clicked on the thumbnail view screen yet? The strange thing is that when we click on this, we can see all the pics, so FM must know where they are, right?

Actually, this is not the case. The thumbnail is physically imported, even when you select "only store reference to file". So even if you would delete the original file, the thumbnail in FM's container field would still be intact.

Regards,

Peter

This topic is 7052 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.