Jump to content

dstichbury

Members
  • Posts

    7
  • Joined

  • Last visited

dstichbury's Achievements

Rookie

Rookie (2/14)

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

Recent Badges

0

Reputation

  1. Hi, I have a relationship calculations set up between two databases: monday = :user_mon_calc tuesday = ::user_mon_calc The calculation for 'Monday' is - DateToText(start_week)&"_"&username and 'Tuesday' is: DateToText(start_week + 1)&"_"&username etc etc and the calculation for user_mon_calc is - DateToText(activity_date)&"_"&username In my master file i have a portal for each day of the week, which i want to list all records that have the corresponding daay and username. The above seems to work when just displaying the correct rows, however when it comes to entering data into any of the fields in the new row on a portal, it throws up an error message saying that the above relationship is not valid and must be changed before i can modify the field! any ideas? Thanks! P.S I'm a bit of a filemaker newbie so i'll need a idiot proof explanation.
  2. Peter - that is great and makes complete sense - thanks. BUT! - is there anyway i can acheive this from within one interface, ie without having to have 'entries' open. Can the user click on a button and bring up a page that is still in 'Main'? Many thanks!!
  3. Hi there, The portal I'm using is for use at the user end of our database. People enter timesheet information creating new rows for each job they do. - very simple! The problem I'm having is that we need to include a page worth of free-text description boxes that pertain to each entry into the portal, which ideally should be entered from within the same database. If i have my portal on one layout, is there anyway of having a button that can switch to another layout which has the free text boxes layed out, and these boxes relate to one specific row on the portal. I've started trying to create a script which copies the unique job ID number that is created when a new job is made, then switching layouts and somehow searching under Job ID so the pertinent text boxes are displayed. I'm pretty new to filemaker/databases so idiot-proof descriptions might be needed! many thanks
  4. Hi bikergeek - thanks for posting. I'm quite new at filemaker so apologies for being a bit slow. I've created a relationship where title is the match field, and then defined language as a look-up from the title relationship (is this what you meant?) I've then defined the ID field as data_dbname::ID, however when i type in the language it just inserts the first ID number that exists for that title. I'm sure i'm being very stupid - any ideas? Thanks
  5. Hi there, I'm sure there is a simple solution to this, so any thoughts would be much appreciated. I have a database with 3 fields, Title, Language and ID This is relating to another database, where these values would have already been defined. Users will not know the ID, but will know the title and the language. I have created a relationship between the databases, with Title being the key field When someone types in the Title, I have a pop up in the language box that lists the possible languages that the particular title could be. When someone chooses the language how do I get the unique ID that corresponds to that combination of title and language, as determined in the orginal database, to auto-enter into the ID box? hope this makes sense! Thanks
  6. Thanks - I understand the principal, would you mind briefly going over the second part, creating a self-relation and how I'd go about this? Many thanks Dominic
  7. Hi there, Is there anyway I can use the 'unique' validation idea, but dependent on a combination of two fields, for example, say I've got two fields, ' Title' and Language' I will need to create a new record for each new title, and it's corresponding language, but I want to make sure that I cannot create two records with the same title and language. Would i need to write a script in order to do this? Many thanks
×
×
  • Create New...

Important Information

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