Jump to content

Withan

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Withan

  • Rank
    novice
  • Birthday 02/18/1965
  1. Second Field was wrong type: number instead of text. AAARG!
  2. I am trying to search an inventory file. I've included a field for Jewelry Type ID. I am using an unrelated file which has an ID field and a name field. I've set the value list to draw its first field from "Jewelry ID" and the second field "Jewelry Name." Then I set it to only show the second field. It only shows the first record. The only way I can make it work is to use only the first field, "Jewelry ID." But that won't help the user, picking from "1,2,3,4,5,6, or 7." I can't figure it out.
  3. Each Portal has different fields in different orders with different buttons. For instance, their is no color or clarity for a pearl, but it has type, nature, etc. Also some fields need different value lists. To enable easy entry for the type of inventory, different portals were necessary with different fields. The second portal gives an overall list, to allow the user to see everything that has been entered in that batch of items. If the user needs to add or correct something, he can go from the general portal to the specific. I guess I could have named the portal, but it would have been
  4. Okay, as I do about 50% of the time when I post a problem, I solved it myself right after writing! I gave an object name to the first field of each of the specific portals, and went to that. Then everything worked. This may be the only reliable way to go between portals with scripts in FMPro 9.
  5. To allow entry of different types of products into the same inventory table from the same parent (one invoice from a supplier), I have created multiple portals to the inventory table: (Diamonds, Emeralds, Rubies, etc.), each on a different tab. Also on the same layout, I have a simple portal that shows all the items, regardless of type, so the user can see all entries in a list. What I want to do is be able to place a button in the general portal that will then open the appropriate tab and go to the correct portal row for that item. I've got the first part, through an If-Else If-Else
  6. I see what I did wrong. I should have selected "Mailboxes" for "Include only related values starting from...!" I was trying to limit the returned values with the same file I was coming from. And to think I already wrote a huge sript and two layouts to do it the 1998 way, with a portal selection scheme! I kind of like how it came out my way, but your way sure is easier. Good idea about the lookup, so if an employee gets deleted from contacts for some reason you stilll have the name recorded. Going from 1998 to 2008 will contain many challenges! I still have to rewrite the program t
  7. I am trying to create a pop-up value list to insert an employee ID into a field on an unrelated table (Mail Boxes), so the ID of the employee who opened the mail can be verified and stored. Problem is, employees are in the Contacts table, with all the other contacts. (I thought this would help reduce the number of layouts, fields, etc., especially when hiring an employee already in contacts.) When I make the value list use the fields from contacts, everything is fine, but I get a list of ALL contacts, not just employees. Everything I have done to try to reduce it down to just employe
  8. I am re-writing a jewelry wholesale database solution, and need a replacement for Troi Grabber. Basically, I need to be able to take a photo with an attached camera and place it into a field, from within Filemaker. I would also like the same ability for a flatbed scanner. Press a button, scan into a container.
  9. You want to make an email in a separate table. Good idea. Then you want to send it to every contact in your contact table which has a certain characteristic or characteristics. ("Buyer", "Female, tall, blonde") You need to figure out what characteristics you want to choose from, and then make a relationship between contacts and email using the characteristic as a key. Then you can populate your To: field, or preferably you Bcc field with a list of the related email addresses. FMPro has a list function that would work perfectly. There are other methods, including doing it in the co
  10. Now we add a concatenated (based on two fields) relationship between policies and the Broker_License_Chart. Only records that match the broker AND the state will show. We also add another separate relationship to States so that we can shot the state name and abbreviation once we choose the state of the policy. Adding some new fields to allow choosing state and broker by ID instead of name... Of special note, by using a pop-up menu for the broker ID and state, and a special related value list that only shows the second field (company name and state abbreviation), the ID's are stored i
  11. First your Broker_ID is a Number field in one table and a text field in the other. I will change this. Next, your relationship between policies and brokers is based on the company name. A no-no! What if you change the company name just a little? Also, this same relationship is a many-to-many relationship. Also a no-no. You need a joiner between the two. Unless only one broker to a policy? That seems more likely. Will fix. Also, you are putting your broker into policies by name, not ID. Do you want this to be a permanent relationship? If so, you have to do it by broker
  12. I wrote a system in 4.1, which has been ported to 6, which includes a function to allow a high-line video camera to take pictures and insert them directly into a container field. This was done with Troi Grabber. I am getting ready to re-write the entire database and want this same functionality, but Troi Grabber is no longer supported. I had heard 8 and 9 had this built in, but I can't find it. Especially, I want to be able to automatically choose between the iSight camera, and a high level camera hooked up via a video capture card currently installed in G3 Tower. Will want to replace thi
×
×
  • Create New...

Important Information

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