Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

Looking to make a custom Field


This topic is 5843 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Ok, so I'm a noob at FileMaker Pro 9, but my company has asked me to set up a client db with it. I've come a long way, but now I can't figure out how to make a field type that I need. Here's what I'm needing:

I'm looking for a field that can hold:

1. Dates

2. Notes that correspond with the dates

3. A scroll bar that will show me all the dates/notes that belong together.

Dates should be to the left, notes to the right. I need clear lines between each individual date/note, as it would confuse coworkers otherwise. I've purchased a book, looked through fm.com's forums, and not found a way to do this field type yet.

Anyone able to help me? Thanks!

Posted

Welcome to the Forum.

Set up a separate table related to clients:

Clients::ClientID -> Notes::fk_ClientID

Notes fields:

NoteID

fk_ClientID

Note_Date //Set up as a creation date

Note

Now put a Notes portal on your Clients layout showing Date Filed and notes Field. Remember to set the portal to 'Allow Creation of New Record' on the Notes side.

Depending on how extensive the Notes will be set your portal to the appropriate height (like 50 pixels = 3 lines approx.) Depending on how much real estate you want to use set up the number of current notes you want the portal to show. Sort the portal by date in 'descending order' if you wish to see the last note first.

hth

Posted

Basically, it is a couple fields, a Timestamp field (which is a combination of date & time, but can be used as either) and a Notes field (Text field). The live in a child table of whatever your relevant main table is.

I like to script creation of notes, so that the portal you generally view them in can be sorted descending by timestamp; so the latest notes are at the top.

This may all be a little over your head at the moment. But this is the simplest example possible.

Notes_simple.fp7.zip

Posted

Are these part of the Relational Databases; One Table Occurrence, One Found Set? I'm using the Missing Manual Series as my guide, and I think it's pointing to this same kind of info. Hard to tell for sure though, it's not uber clear.

Posted

It is a relational database, with 2 tables, 2 table occurrences. Though you could certainly have more. It is a simple example of creating "child" records by script, so that a descending sort of the portal works well.

Posted (edited)

Ok, so I've run into another problem. I've managed to create the relational database, but I must be missing a step. I am not being prompted to "allow creation of new record." I see no radio buttons or check-boxes with the option. What am I missing? Mind giving a more detailed step-by-step?

Edited by Guest
Posted

I am not being prompted to "allow creation of new record." I see no radio buttons or check-boxes with the option. What am I missing? Mind giving a more detailed step-by-step?

Edit the link between the two TO, in the relationships graph you will see it.

Posted

Now it's trying to create an extra instance, and still won't let me edit the field once I go back to browse mode. Not finding much in the book to help either.

Posted

In layout mode, right click the field you can not enter, chose 'Field/Control', then Behavior and look at 'Allow Field to be Entered:' and make sure Browse is checked.

You could also upload a cloned copy of your file for us to take a look.

hth

Posted

Your file is missing some important info.

You should have at least a minimum of 3 tables.

Company

Contact

Notes

Each contact should be associated with a company. Then it seems as each note is assocaited with a contact.

Company --< Contact --< Notes

Company::kp_CompanyID = Contact::kf_CompanyID

Contact::kp_ContactID = Notes::kf_ContactID (Allow creation of record on the child side (notess side) of the relationship )

Posted

As John indicated you really need 3 files to do this properly. You initially indicated that you wanted to have your notes lined up with the Date and note next to each other. I've made a few adjustments. They may not be exactly what you want, but should get you going in the right direction.

Contact_List_Ryo_mod.zip

Posted

How did you manage to get it to do that? I'm trying to get my original database to do it, but it's not taking. I don't know why I'm having so much trouble with this...

Posted

wow, that's actually really good! I must not be understanding the "fk_" concept. The Missing Manual hos not even mentioned it where I am. Could you maybe explain how that works? I'm hedging bets that that will fix my confusion.

Posted (edited)

You need to look at your relationships. You had the relationship as:

ClientList:NoteID->Client::NoteID

ClientList::NoteDate->Client->NoteDate

and another field as well.

All you needed was:

ClientList:: ClientID -> Client::fk_ClientID

I would suggest a little reading material before you get to far in to your design and then things start to fall apart because of structure issues. It is better to invest a few hours now then 100's of hours later trying to fix or re design your database due to structural problems.

http://www.filemaker.com/help/MacTOC8.html

http://www.foundationdbs.com/ Read the White Papers for FM novices.

***************************

fk simply indicates 'Foreign Key' vs 'Primary Key.'

Many developers use pk_Fieldname to indicate it is from the primary (Parent) table and fk to indicate it is from the Foreign (Child) table.

Edited by Guest

This topic is 5843 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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