Naomi Dathan's Blog, page 4

Your developer should give your users an

Your developer should give your users an application, not a database. Yes, under the hood, the information should be neatly organized and categorized. But your user shouldn’t have to see or think about the data. He should have an intuitive experience:

“Oh, hello” (your Filemaker Pro application should think, but probably not say) “I see that you are Mark. You almost always need to see this particular set of data, in this order, with these options to continue your usual work flow from here.”

Your database should seem as friendly and helpful as this giraffe. http://ow.ly/i/lruky

It’s Not Their Fault

If multiple staff members make the same data-entry errors, put the blame where it belongs: on your improperly designed database. #Filemaker

If multiple staff members make the same

If multiple staff members make the same data-entry errors, put the blame where it belongs: on your improperly designed database. #Filemaker

Labels Have Their Place

We all get tired of labels and categories. After all, life is complicated and human activity is messy.

However, when it comes to tracking your business information information, labels and categories are your best pals.

If your staff members were working in an Excel spreadsheet, they had some flexibility. Maybe you had a column for phone types, but sometimes they entered “cell”, sometimes “mobile. Sometimes “home” and sometimes “landline.” Maybe in the category for certifications, they sometimes wrote the credential out: “Hog Calling Regional Certification” but sometimes used the “HCRC” abbreviation.

But now you’re ready to step up your business information processes. You want your data captured quickly and accurately, and you want to be able to retrieve it instantly. When you’re deciding whether to apply for Elevated Hog Calling Status for your company, you need to be able to push a single button and generate a report of how many employees have their HCRC certification and when those certifications expire.

Here’s where “Normalization” kicks in. To get your report to run properly, your staff members need to enter the consistently. And here’s the challenge. You probably hire the best, but they are busy. Their days consist of a million small tasks besides entering data in that one field. Their days may consist of entering data into many fields, all with their own specific limitations.

Free them up to focus on their jobs by ensuring that your database does its job. Instead of allowing (requiring) users to enter the type of phone, let them click the appropriate radio button: “mobile” or “home.” Give them a dropdown list to select the appropriate credential. Now your reports will run properly because you’ve eliminated the variations and potential for typos.

Filemaker Pro has a variety of built-in ways to ensure the normalization of your data, from dropdown menus to check boxes to validation for character limitations and numbers instead of letters.

Make sure your developer takes full advantage of these. If errors occur repeatedly, don’t blame your staff members. Blame your database, and see that it gets fixed.

We all get tired of labels and categorie

We all get tired of labels and categories. After all, life is complicated and human activity is messy.

However, when it comes to tracking your business information information, labels and categories are your best pals.

If your staff members were working in an Excel spreadsheet, they had some flexibility. Maybe you had a column for phone types, but sometimes they entered “cell”, sometimes “mobile. Sometimes “home” and sometimes “landline.” Maybe in the category for certifications, they sometimes wrote the credential out: “Hog Calling Regional Certification” but sometimes used the “HCRC” abbreviation.

But now you’re ready to step up your business information processes. You want your data captured quickly and accurately, and you want to be able to retrieve it instantly. When you’re deciding whether to apply for Elevated Hog Calling Status for your company, you need to be able to push a single button and generate a report of how many employees have their HCRC certification and when those certifications expire.

Here’s where “Normalization” kicks in. To get your report to run properly, your staff members need to enter the consistently. And here’s the challenge. You probably hire the best, but they are busy. Their days consist of a million small tasks besides entering data in that one field. Their days may consist of entering data into many fields, all with their own specific limitations.

Free them up to focus on their jobs by ensuring that your database does its job. Instead of allowing (requiring) users to enter the type of phone, let them click the appropriate radio button: “mobile” or “home.” Give them a dropdown list to select the appropriate credential. Now your reports will run properly because you’ve eliminated the variations and potential for typos.

Filemaker Pro has a variety of built-in ways to ensure the normalization of your data, from dropdown menus to check boxes to validation for character limitations and numbers instead of letters.

Make sure your developer takes full advantage of these. If errors occur repeatedly, don’t blame your staff members. Blame your database, and see that it gets fixed.

Hey . . .

Build separate #Filemaker layouts for each device, but when in doubt or rush, build for web or mobile device.

Build separate #Filemaker layouts for ea

Build separate #Filemaker layouts for each device, but when in doubt or rush, build for web or mobile device.

Poor primary key planning is an expensiv

Poor primary key planning is an expensive time-bomb. Make your #filemaker dev explain this before hiring.

Use #Filemaker Server’s backup schedule

Use #Filemaker Server’s backup schedule as primary backup. System level backups can corrupt files.

Your #Filemaker Developer should take planning Very Seriously

Your #Filemaker Developer should take planning VERY SERIOUSLY. Anticipate the eventual size, potential complications, reports.