Thanks Carl and Walt for your input. Working with Walt's idea of creating a
race_.102 file - without going too far beyond the scope of this listserve,
what's involved in making an extra relational ebase file? If I envision such
a file, I'd make it something like the payments file, where each race entry
from year to year is like a payment entry. I kind of suspect it would be a
big job to do - your thoughts?
cheers
kevin
-----Original Message-----
From: Walt Daniels <[EMAIL PROTECTED]>
To: TechRocks Support <[EMAIL PROTECTED]>
Date: Monday, February 26, 2001 12:55 PM
Subject: [support] RE: Custom vs. Names
>There is no customs file. The custom layouts are in the names files. Of
>course you can refer to fields in any other file and put them on one of the
>custom screens. So there is no need to create new fields for much of what
>you want to track. There are already fields present. It is ALWAYS a bad
idea
>to put age into any database. Record the date of birth and use a
calculation
>to display the age. Look at the bio screen for an example of what you want
>to do. You might even start by making a copy of it and adding some new
stuff
>and deleting a lot of extraneous stuff. It will show you examples of
putting
>fields from different files on one screen.
>
>The next thing you want to consider is if this a one time deal or if you
>will be doing it again next year. For this you might want to create a new
>file, race_.102, and provide for multiple years data.
>
>> -----Original Message-----
>> From: Kevin Haskins [mailto:[EMAIL PROTECTED]]
>> Sent: Monday, February 26, 2001 12:43 PM
>> To: TechRocks Support
>> Subject: [support] Custom vs. Names
>>
>>
>> Hi all -
>> I'm using v1.02, and making use of one of the custom screens to
>> record some
>> data. We're running a road race, and we want to keep track of the race's
>> year, and the racer's name, age, sex, bib #, and t-shirt size. I know
some
>> things, like age and sex, can already be found in the Bio screen. But for
>> the sake of keeping this race info separate, and viewable on one custom
>> screen, I thought I would go ahead and make new field definitions for the
>> items listed above (Race Year, Racer's Age, Racer's Sex, Racer's
>> Bib Number,
>> and so on). My question is: does it matter which file I use to define the
>> fields - e.g. the names file vs. the customs file? I don't intend
>> this to be
>> a permanent place of data storage; it is more of a one-page
>> interface to be
>> used for a single year that has all the info in one place - if
>> that matters
>> to this question at all.
>>
>> Cheers
>> Kevin
>> Portland Trails
>> 1 India St.
>> Portland, ME 04101
>>
>>
>> ------------------
>> 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
>> ---------------------------------------------------------------------
>>
>>
>
>
>------------------
>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
>---------------------------------------------------------------------
>
>
------------------
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
---------------------------------------------------------------------
