Export all data to Excel or Access

I am trying to export all of our data to an excel or access file. I am able to view all of the contact data and last donation however I am unable to get all of the log items out. Any suggestions???

Use New "ebase data extractor" Utility?

As a part of the automation in the new V2.8 of ebase, there is a stand-alone "data extractor" utility that runs in FileMaker Pro V6 to remove ALL key ebase data.  That data is placed in 10 FileMaker databases that are VERY much simplified compared to the starting V2.2 files. 

That still leaves you to export data from those new databases into CSV or whatever format you want.  But this is a LOT easier since those databases are a LOT more simple, no security settings, only 3-4 scripts each, etc. 

I had the idea of generalizing this utility to also allow the user to generate CSV files, etc.  but that hasn't been done yet, as I felt it wasn't essential for the main focus on supporting ebase V2.2->V2.8 "upgrade" automation. 

This might get you to a better position?

Which version of ebase?

Can you indicate which version of ebase you're using?

At LEAST in V2.20, I'm pretty sure one of the "log export" reports can do this for you.

However, I think this particular report may NOT have been present in V2.03...

FYI, if you have contacts with MULTIPLE "locations", etc, it's POSSIBLE that the contacts export will only contain the PRIMARY location information...

"Export all data" script

While working on the new V2.8 of ebase, I could SWEAR I'd run across and "export all data" script.

It might take me a short while to search for an find that script.  It does NOT appear to be accessible via "maintenance/developer" scripts.

I'll report back after I get a chance for a search...

"Export All Data" script follow-up

This script is typically NOT available via the standard ebase layouts provided to most users.  It CAN be run during a "developer" style database session started using a full copy of FileMaker Pro and logging in using the DevLogin.fp5 file as the starting database. 

In addition, there is one script error present in this script, so you might have to be waiting for an error message at this point with the appropriate "user response". 

So this script might not be the BEST choice. 

I'll post another comment about possible use of the new "ebase data extractor" utility for this situation.