Two 'HowTo' Questions

[Dotnet]

Hello all and welcome from a FM Virgin!!,

I have just 'come across' Filemaker and currently running a trial version for evaluation and have a couple of questions.

1) When entering data into a field how can I make sure the actual data stored is in a certain format namely the first letter in each field is a capital lettter eg Name not nAME or name or NAME

2) I'm using a sample project to help me learn FM which is a basic membership system for a small gym. I'm having problems desiding how best to structure the data entry to allow the following (and of course the different pricing levels)

Namely:-

INDIVIDUAL (1 members)

JOINT (2 members)

CORPORATE (upto 5 members)

Obviously, I need a place for the info for the second member when a joint membership is 'chosen' and additionally I need a place for five members in the corporate option, but the company having the main membership number.

I have broken down the data into the basic tables but I'm falling over with the Primary Key (membership Number) I'm assuming that the standard way is to have one membership number for all individual 'accounts' - beit one member or 5 for the corporate.

Thanks in advance

Matt

[mr_vodka]

Hello Matt,

Welcome to the forums.

1) When entering data into a field how can I make sure the actual data stored is in a certain format namely the first letter in each field is a capital lettter eg Name not nAME or name or NAME

In your field definition, use the auto-entry option of "Calculated Value" with Proper ( thefield ) and with the checkbox, 'Do not replace exisiting value...' Unchecked.

This will take whatever the user has entered and convert it to the format that you want.

2) I'm using a sample project to help me learn FM which is a basic membership system for a small gym. I'm having problems desiding how best to structure the data entry to allow the following (and of course the different pricing levels)

Namely:-

INDIVIDUAL (1 members)

JOINT (2 members)

CORPORATE (upto 5 members)

Obviously, I need a place for the info for the second member when a joint membership is 'chosen' and additionally I need a place for five members in the corporate option, but the company having the main membership number.

I have broken down the data into the basic tables but I'm falling over with the Primary Key (membership Number) I'm assuming that the standard way is to have one membership number for all individual 'accounts' - beit one member or 5 for the corporate.

I think that you should set up two tables in a one to many relationship with Memberships being the parent and Associated Members being the Child. You can have a button that runs a script that will check the 'membershiptype' field and depending on the value, could restrict how many new child records can be created.

[Dotnet]

Hi John,

Thank you for your prompt reply.

Love the name by the way - reminds me of the time I found a bottle of the good stuff buried in a wall during a refurb of my local pub two days after turning 18, had been there 11 years! Had a job, legally allowed to drink with a bottle of rocket fuel - those were the days.

I was so close ref your first response, I was looking at doing something with left(text) and upper(text) didn't see proper(text) aarrgghh!

With the second point I think I have got myself confused and gone around the houses a bit. I need to have a re-think and perhaps repost.

Again thank you for giving up some of your time to answer my post

Matt