We have reset all users FileMaker related profile fields. Please take the opportunity to update your information,  this will provide background to members whom read your posts. Click here.

Jump to content

mcsebot

Members
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mcsebot

  • Rank
    newbie
  • Birthday 12/18/1961
  1. I'm not explaining this correctly and I don't know how to. Thank you for your feedback. If I happen to figure out a better explanation I'll post it. Happy Holidays...
  2. Thank you for the quick reply. I do have some users that need to see DB2 and will be working in it directly. On the server I have "List only the databases each user is authorized to access checked. If I Authorize each user for read only in DB2 so they can see the contents in DB1 they're all going to see DB2 in the Launch Center. Is there a way I can provide Authorization at the DB level?
  3. I suspect this has been answered before but my searches aren't finding what I need. I have two databases and I'm linking fields from DB2 to the interface in DB1. I have external authentication going. When user connects to DB1 their asked for authentication for DB2. I don't what them to have access to DB2 and I don't want them to see DB2 as would happen if I were to even give them read only. I've setup the External Data Source between the two FileMaker databases. What might I be missing? I should be able to display data from other databases without giving the user read access to all the databases. I hope you understand what I'm trying to say and thank you for any help. Where's my Boot-Camp, ~MCSEBOT
  4. Haven’t found post of this problem so here I go. Windows Server 2008 R2 Standard Everything ran nominally under Server13, external authentication After upgrading to Server14 (following instruction meticulously) none of the databases would show up until I unchecked “List only the databases each user is authorized to access”. When unchecked all the databases show to all users but they can only enter the one’s they have access to. This tells me that the External Authentication is still working properly but the File Display Filter is no longer working. Note: this happens with all client connection types, Windows, Mac, Web-Direct, and GO. Any help would be appreciated.
  5. Never mind I fixed it. Somehow the container was pointing to a diffrent directory. Given the new pictures were already working from the corret path, I copied all the older pictures into the new path. :-)
  6. Ooops, just notice that the file name in the container preceded by the word "Missing:" Now I have to figure out why it thinks the file is missing only when accessing remotly. Maybe a permissions problem.
  7. One of my tables has a container with pictures in it. The pictures (mostly .jpg not that it matters) all showed up just fine. I moved them to external un-encrypted storage and now the container shows the file but not the picture. If I close the DB on the server and open the DB locally the pictures all show up correctly. Once I mount the DB with the server, all clients see the file in the container but not the picture. Any new records/pictures added show up just fine. I would like to get all the records to show the files as a picture like it was before I moved them. Note: I’ve done this with two other containers in different tables and they maintained their picture status. Don’t know why this one acted differently but I need to fix it. Thanks for any help,
  8. Found what I needed.... Global Fields Global fields are simple, and a great blessing. They have been used as variables in the past, though there is little need for this particular use now that versions 7 and 8 of FMP have been released. Still, they are extremely beneficial and there are some vital things you need to know about them before you start coding: o Global fields are used when every record in a table requires exactly the same information. If the value of a field will always be the same for every record in a table and for every user, then a global field may be the ideal choice. It stores the information in one place only, but treats it as though it were a field in every record. This eliminates unnecessary overhead and allows for a much more streamlined database. o Under some circumstances the data contained in globals can be lost, so beware. For example, when saving a clone of a file, the data in global fields is NOT saved with the clone. The global fields are saved empty. o Each user gets a separate, private set of global fields. Global fields will not retain their values after shutdown. Many FMP newcomers are puzzled when they reach a point where they begin to try out their database(s) with multiple users. They discover that information contained in global fields is not correct when they sign in again after quitting FMP. This is because there is one master set of globals contained in the actual file. The information contained in these fields is that which was placed there by the person who developed the database(s) or who last accessed it as a single user. When that file is shared so that other users can access it, whether by just turning on sharing in FMP, or by serving the files with FMP server, each user gets a fresh set of private global fields that are loaded on startup with whatever information was originally contained in the master set before the file was shared. This means that vital information that is different for each user cannot be stored in a global field. The only way to change the information contained in the master set of globals is to open the database(s) as a single user (not by accessing them through FMP server), and then change the information in the global fields. o DO use global fields to store static information or graphic objects that will never change and will be the same for every record, such as a company logo that will appear on each layout. o DO use global fields as the primary key for a dynamic relationship such as a filtered portal (the user selects specific criteria which limit the records the portal can show). o DO NOT use global fields to store user settings. Each user will expect to find the same settings each time he logs in, but the data in his personal set of globals evaporates when he logs out. o DO NOT store constants for calculations in globals if there is any possibility at all those constants might one day change. For example, you can store the value of pi in a global field. There is little chance that will change. But do not store constants such as a tax rate in a global field. We all know what happens to those!
  9. Boy, this is exactly the problem I’ve been fighting with for three days. I’m working with a database sitting on a FileMaker Pro 7 Server and when I place a graphic into a global container the next time I launch my remote FileMake Pro 7 program and then open-remote the database the global containers are empty. I’ve read through ALL the FileMaker Pro help and there’s not one word mentioned about this happening. I suppose it’s covered in the Server Help… I’ve tried using a normal field to hold the graphic and then creating a global calculation that’s equal to the normal container but this does not work. It seems that a calculation cannot hold a graphic. What’s this about restarting the server? Can I get my global graphics loaded permanently if I have the server restarted? Do I have to have the database open with the graphics loaded into their containers before restarting the server? Thank you for any help, ~mcsebot
×

Important Information

By using this site, you agree to our Guidelines.