Jump to content

goostree

Members
  • Posts

    47
  • Joined

  • Last visited

goostree's Achievements

Contributor

Contributor (5/14)

  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In
  • First Post

Recent Badges

0

Reputation

  1. I would like to send a mass email from Filemaker to Outlook, but use the bcc feature in Outlook so everyone doesn't have to scroll through a huge list of email address at the top of their email. There is a cc feature in the Sent Email dialog box, but is there a way to do a bcc? FileMaker Version: 5 Platform: Windows XP
  2. I'm curious. Why do you need to do this with a calculation instead of the format field options?
  3. So you have a record for every picture and a field to indicate which month the picture was received or used in? How are your months entered? Do you have the month names(January, February, etc.) or a date(3/5/2002)? You mentioned that you compare the pictures from both months to determine whether or not they were used. How do you determine this? Is there a field that indicates that the pictures were used, or when they were used? Or is a picture listed under both months if it was used?
  4. Each record you need to delete needs to be found separately? Or is there a find you can do that will find multiple records that need to be deleted? Also, how do you keep track of what records you have used and what records you haven't used?
  5. I agree with DJ. More info on the other relationships you're using would help greatly. For instance, how are your records created in Third? How do they relate back to Main? Will the records in Third relate back to the same Main record as the records you are trying to create in Related?
  6. I'm going to take a stab in the dark here and make the assumption that your lists are data contained in portals. It sounds like you have the portal (list) on layout 2 set up with the correct field(s), but still using the relationship from layout 1. Make sure you change the relationship on the portal to match the relationship on the fields.
  7. There might be an easier way to do this, one not involving 14 different finds and set fields. Probably depends on what kind of finds you are doing. Do they change or are they always the same finds? I'm thinking there should be a way to duplicate this functionality with self-join relationships. Don't know if it will work or not. Some more information about what you are needing to do would help.
  8. Make a script in the file you're opening that refreshes the window and brings it to the front. Then add a script step to the end of your original script that performs the refresh script in the newly opened file.
  9. Look up heirarchical value lists on John Mark Osborne's www.databasepros.com. It will allow your value lists to change based on the value of a field. These are also called conditional value lists. I think there has been a thread on this recently somewhere in this forum. Check the value lists forum.
  10. To be quite honest, I have no idea how this works. I saw it on another thread and thought the person posting it didn't have a very good understanding of calcs. I was about to explain to the person that they needed a test for their If statement, so I tried it out in order to better prove my point when I shared my wisdom with them. Good thing I tested it first, because it worked like a charm. Don't know why, don't know how. I would be very interested if someone could explain it to me.
  11. You could make a calc field that would enter the current date anytime one of your student fields is updated. Then you can perform finds for a certain date or a date range to see which student's records have been updated lately. I'm not sure which database you would put this calc on. Maybe a more experienced user could help out with that. This calculation needs to be unstored to work. Here is the calc: If(Field1 or Field2 or Field3 or Field4, Status(Current Date), Status(Current Date)) This calc will tell you when any of these fields is updated. If you want to get more specific, you can make a calc field to hold a date for each individual field rather than lumping them all together. You also don't have to have it enter a date. You can have it enter anything. However, if you have it enter "X" or whatever that will stay there unless you remove it somehow. That could get a little confusing. Probably best to stick with a date so you know not only that it was updated, but when it was updated.
  12. Check to make sure your portals are using the correct relationship, as well as the fields in the portals. I vaguely remember getting duplicate portal rows because my fields were coming from one relationship and my portal from another. They should be using the same relationship. Hope this helps.
  13. Glad you got it fixed. Very interesting problem, and I have no idea why the global was causing the problem. I also don't know about the attachment problems. I've never tried to attach anything. I think I looked in FAQs once, but didn't see anything about it. Maybe a post in the "FM Forums Feedback and Support" forum would get an explanation.
  14. Add a field that will contain some sort of ID number. Create a new relationship based on the ID number. Enter your ID information into the ID number field. Make sure that if you want records X, Y, and Z to relate to one another, you enter the same ID in the ID number field. You can view all the related records through a portal.
  15. Anytime you use relationships it's best to use some field that doesn't mean anything to relate records to one another. Basing your relationship on the phone number is fairly easy to work with now, but anytime Billy Bob's phone number changes you have to remember to manually go back and change Angelina's phone number also. Otherwise your relationship will be broken. It's better to set up an ID field with random numbers that don't mean anything.
×
×
  • Create New...

Important Information

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