28-Jul-2006, 08:31 AM
|
 | Guest | | | | | | | | |
| Re: Is there a character limitation of 200 characters per entry?
On Thu, 6 Jul 2006 16  02 -0700, SRE
wrote:
>Hi John,
>
>Thanks for that info.
>
>I suppose I should be clearer about what we really want Access to do.
>
>Our FMP database is not doing what it's meant to, because it lost features
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/12564-there-character-limitation-200-characters-per.html
>when it was moved onto a new computer, so there's no loss there. I've
>already imported the data into an Access table without any difficulty.
The data is one thing. The Access application is a different one.
>In FMP or Access, at the moment it is not possible to extract data on new
>and renewed members for each past year, but we would really like to be able
>to do this in the new database.
Access should be able to handle this perfectly well.
>If it's not good practice to overwrite data each time a member renews, does
>that mean I would have to re-enter the membership details each time a member
>renews?
No, it does not. Please reread my message. In Access - UNLIKE FMP -
you would store this information in *two separate tables* within the
Access database. You would store the membership details, once only, in
a Members table; this table would have one record for each member.
The renewal data would be stored in a *separate* table, with a
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=12564
MemberID field as a link to Members but containing *NO* member
biographical information; each renewal would have a new record. For
example you might have a Membership record like
Members
MemberID 239
LastName Jones
FirstName Kevin
Address 123 Main St
City ...
Renewals
RenewalID 8132
MemberID 239
RenewalDate 7/11/2005
Payment $25
RenewalID 9446
MemberID 239
RenewalDate 7/1/2006
Payment $28
This would typically be edited and displayed using a Form based on
Members, with a Subform based on Renewals.
>If so, the database would just keep getting bigger and bigger as I would
>need to keep using the old data to search whether the member is a new or
>renewing member.
Bigger and bigger. Note that 10,000,000 rows of renewals for 1,000,000
members is starting to get "biggish" for Access.
John W. Vinson[MVP]
 |