[Tech] Re: Supporter database status

[Daniel Melnechuk]

What i have custom built into Filemaker Donor database to deal with  
financial issues are based around the concept of enter the data once.  
What this means is integrating Filemaker donations with both FEC and  
OCPF reporting, as well as QuickBooks. Here is what i have built that  
is working and would need complete replacement since i, as treasurer,  
do NOT want to go back to a time when multiple entries have to be  
made for donations!

So when i make a deposit, FileMaker database generates both the file  
that i need to import into either OCPF or FEC reporting software, as  
well as generates a file that imports the donations as a deposit into  
Quickbooks so the accounts balance as well.

There are some other issues, but what happens above is the minimum i,  
as treasurer, require. And even if i wasn't treasurer, i would  
require it since we already have it. Doing the books is enough of a  
task that you do not want to generate more work that can introduce  
errors.

I think i have made my point so i'll stop now.

The only other issue is security. Will look at the civicrm site about  
that.

Peace,
Dan

On Mar 18, 2007, at 4:38 PM, Jamie O'Keefe wrote:

> On 3/9/07, Jamie O'Keefe <jokeefe at jamesokeefe.org> wrote:
>> Open issues (For CiviCRM):
>>
>> 1.  Does it do what the contributor database does and if not, can we
>> write code to do what Dan needs the contributor db to do?
>
> Seems like it might, but we should need to rewrite custom OCPF
> contributor report code.
>
>> 2.  What features are not in CiviCRM and can we write add-ins to
>> perform those functions?
>
> If not in there, then we can always add to the schema and write code
> to deal with those tables and joining them.
>
>