> > 1. We just imported from V1.03 and there were 1481 records ... when we > converted to v2.02 there are now 2689 records. In looking into this > anomoly, ebase has split all those contacts where the husband / wife > (Partner) has a different last name -- so instead of just one record of > jane doe and harry smith -- there are now three records of jane doe, > harry smith, and jane doe and harry smith. This could pose a problem in > terms of staff entering contributions -- making sure they are accessing > the right record; and in running a query / script where you're looking > for certain kinds of donors -- you don't want all 3 (in essence the same > people) coming up on that list. Doe ebase know the difference? Is > there a way to get back to just 1 record or don't we want to do that? >
I don't have any advise here. > 2. Is it possible to get a description / purpose of each field (with > field name code)? This piece of information is really critical to > understanding which information is meant to go in which fields. It was > a pain not having it in V1.03 and seems even more imperative for v2.02. > Can any one provide this? > A run of the FileMaker field mapping tool was posted at some point. It is probably still there somewhere but probably at 2.0 level. Only the manuals really describe the user visible fields and some of their intent. They are not complete by a long shot. > 3. Re: changing layout formats ... can you only change layout (report) > formats from within the DevLogin file? If so, that seems dangerous. Is > there a list of layouts like there were in 1.03? If so, where is it / > how to access? We want to create our own custom report formats ... does > v2.02 preper that you do them in Word or Excel only? When I enter > Contacts.200 from opening FMPRo 1st, the view layouts is only accessible > in the Reports section -- is it possible to change (ie customize) the > layout of say the Contacts Overview screen? If so, how? > Don't go there. You won't be able to upgrade to the next 2.0x without redoing any changes you make. > 4. Related to the fields request above, in what fields should we place > the names of baord and staff members who know verious contacts for > fundraising purposes. For example, if Gene B knows Contact x and we > want Gene to call Contact x, in what field do we place Gene B so that it > is searchable? So if I want to print out a report of all contacts that > Gene B knows and will call during a phonathon .... how would I do that? > That is what Code Generation is all about. There are some builtin fields but it up to the user to define additional fields that are specialized to how they do business. > 5. Just tried to backup the V2.02 files onto a CD and I'm told that it > can't copy the file -- that it's lock from another function. How do I > back up our files? > Most likely you tried to backup while you still had ebase open. You must close it before you can do backups. ------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------
