Jump to content

Shipbuilder

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Shipbuilder

  • Rank
    member

Profile Information

  • Gender
    Not Telling
  1. Hi Barbara, I took a good look at the example that you posted and believe that it will be suitable for implimentation into the project that I am working on currently. However, I am unable to get it to work properly. I think that due to the flexibility that has been developed into my database that I may be getting confused in the area of "uninvoiced" items (which in my case is "unpurchased" items). I am sending a copy of it to you privately because the database contains some information that is private to my company. Your thoughts are greatly appreciated. Regards, Tony
  2. Sounds like an idea to me. Could you provide an example of what you are talking about so I can get a better idea of how it would work? Tony
  3. Actually, the user doesn't need the ability to "shop" several Requisitions in this case, however, they need the ability to take one Requisition (which contains as many as seven items on one Requisition) and split it out over several Purchase Orders (seven Requisition line items could end up equaling seven different Purchase Orders). Tony
  4. Barbara, Sorry for the delay. I've actually found and fixed the problem. The issue was in the relationship. The requisition table was also related to the PO table via the auto generated requisition number. This would allow a purchaser to pull the data entered on the requisition form into the Purchase order form through a drop down menu that relates to the auto generated requisition numbers. The relationship cannot allow the Purchase order table to create new records in the requisition table or else the original line item serial numbers in the portal become redundant. I had arbitr
  5. Barbara, Yes I have a field named Serial Number that is displayed in the table and it is set to auto-enter the serial number on "creation". Also, yes the serial number is from the same table on which the portal is based. However, this is a requisition form and in the relationship, the requisition number in the child table equals serial number in the parent table so that once the requisition number is selected via a pop-up list on a seperate form, all of the related records are shown via the relationship. I don't have a problem with all of the IDs being the same in a single portal
  6. The portal that I have created has seven rows and each row has a serial number. The problem is that I need each row's serial to be unique. As of right now, the serial numbers auto enter as the same number (i.e. all seven rows have the serial number of 91, but I need 91, 92, 93, 94, 95, 96, and then 97). How would I go about making this happen? Thanks, Tony
  7. So, are you saying that multiple weeks can be shown on the report by using the found set? How would I write a script that picked up the date range as well as the calculated result and show it for multiple weeks? (I'm not saying it can not be done. I'm asking how to do it.)
  8. Attachedment Monthly Hours.pdf
  9. Here is a view of what I currently have in place to help understand what I am asking.
  10. I am looking for a solution to omitting records within a self join relationship. I have a table "Daily Manhours" that holds the daily hours of all employees of the company for several years. Among other fields, I have fields "date", "employee ID", and "total hours". I created two new fields named "week beginning" and "week ending" with a self join relationship to "date". By doing so I was then able to produce a report that gave me the total hours of all employees within a date range where the range would be input by the user: Daily Manhours:Week Beginning Daily Manhours:Week
  11. I am not able to access the value lists through the pop up list. This may be because I am using FMP7? So, I can't tell completely how you were able to get "hull" to work properly. I can however see the relationship that you created in the graph. As it always goes...just after posting I figured it out. Thanks again!
  12. Thanks for the help! I will analyze what you have sent. As for the rethinking, I am doing most of this on the fly without much Filemaker experience at all, so I covet any professional help that I can get, however, there isn't much of that around where I am at. If you have suggestions, I am completely open to them. Thanks again for all of your help and if you don't have a project laying around...please, be my guest.
  13. I apologize if things were cluttered in my description. Attached is an example (which is a cut back version of the project that I'm working on). From the layout "GS Requisition" you will see a form with many fields but the ones I am trying to get to work correctly are as follows: 1)Related To (allows selection from table) 2)ActiveJobNumber (allows a filtered selection from table) 3)Hull (should set based on selection of items 1 & 2 above) "Hull" is a portion of "ActiveJobNumber" that has been determined by a calculation in a seperate field. Three Level Example.zi
  14. I have a layout that has three levels of conditions. The first level is "related to", the second level is "job number" (which is conditional based on selection of the first), and the third is "hull" (which is conditional based on the second). The first and second work great, however, the third only works halfway. This is basically setup as a filter. There are four options in the first level: related to - "vessel", "overhead", "warranty", "facility". Once one of those items is selected, the second level "job number" is filtered into those four categories for selection. Once the second is
  15. The old paper form IS the complication, however, the reason for its use to date (in regards to my company) is because we have a lot of supervisors in "the field" without access to computers and they hand write these to request materials.
×
×
  • Create New...

Important Information

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