i there,
I am looking for someone to help with a DB project for a non-profit org "Slow Food RussianRiver". I have DB experience but the problem I am having is beyond me.
Each month I receive an updated version of our membership in an excel doc. with some new members and some updated addresses. I want to import this file into the Current Membership DB and if there are new members it will add them and if there are any address changes it will update them. Not quite sure how to pull it off.
If you can help please email me [email protected]
thanks much, randi
bobafifi
03-23-2006, 10:38 AM
<tt><tt>Hi Randi,
What version of FileMaker are you using?
FileMaker Pro 8 will import your excel file AND
take the first row as the field headers - very
cool. Would make what you're trying to do a snap.
-Bob
</tt></tt></pre>
bobafifi
03-23-2006, 10:48 AM
Import Excel files instantly
(https://www.filemaker.com/products/fmp/get_started.html)
"Just drag your Excel file onto the FileMaker icon on your desktop and the information will import automatically. You choose which worksheet to import and whether the first row of data in the spreadsheet contains field names or data. Learn more about importing Excel files."
bobafifi
03-23-2006, 11:29 AM
In re-reading your post, are you getting ALL the members each time or only a few members that you are then trying to add to the DB? If the first, then simply creating a new DB each time would be the easiest solution. If the second, then what you're trying to do is merge files: the new info -> DB
In my old version of Dynodex 3.5, there is a "Delete Duplicates" function for removing the redundant entries.
There's some info here for how to do it using FileMaker (scroll down) https://72.14.203.104/search?q=cache:jEtrYHtzS1AJ:www.experts-exchange.com/Databases/FileMaker/Q_21560581.html+filemaker+pro+delete+duplicates&hl=en&gl=us&ct=clnk&cd=5&client=firefox-a
Hope that helps,
-Bob
bobafifi
03-23-2006, 12:08 PM
(from the Filemaker Pro 8 help)
Contents > Identifying duplicate values using a self-join relationship
Identifying duplicate values using a self-join relationship
This procedure identifies "extra" instances of duplicated records. You specify the criteria that determine which is the primary record.
This procedure uses a self-join relationship and a calculation field referencing the relationship to determine which records are duplicates.
To find duplicate records except the first instance:
1. If you plan to delete the duplicate records that you find, make a backup copy of the file.
For more information, see Saving and copying files.
2. Identify a field that determines a unique entity in your file.
For example, in a Contacts database, the Last Name field is probably not a good choice, because you might have several people with the same last name. Social Security Number is a better choice. You can also create a calculation field (returning a text result) that combines data in several fields to make a unique identifier. An example formula is First Name & Last Name & Phone Number.
3. Define a self-join relationship.
Use your chosen identifying field as the match field in both tables in the relationship. For more information, see About self-joining relationships.
The primary record is the first matching record according to the sort order defined in the relationship.
4. Define two fields:
Counter, a text field with an auto-entered serial number (select Serial number and accept the default values for Next and Increment by).
Check Duplicates, a calculation field with a text result, with the formula:
If(Counter = table1::Counter, "Unique", "Duplicate")
5. Choose Records menu > Show All Records.
6. Click the new Counter field, choose Records menu > Replace Field Contents, and Replace with serial numbers. Again, accept the default values. Select Update serial number in Entry Options, and click Replace.
This will assign a serial number to all existing records in your database. Serial numbers will automatically be entered in new records.
7. Perform a find for Duplicate in the Check Duplicates field.
The first record in any series of duplicates now holds the value "Unique" in the Check Duplicates field, and all duplicate records within the same series are marked "Duplicate".
Important Records with no value in the match field will be flagged as duplicates. Once set up as above, this system will identify duplicate records automatically as they are created.
Contents > Identifying duplicate values using a self-join relationship