> > > I know that there is no support offered for the beta version of eBase 2, > but I have a general strategy question about eBase versions. I'm just > starting out; new organization, new database, new lists, no legacy data > or systems. I like what I've seen of eBase 2, especially running with > Mac OS X. Is it reasonable to start our system with the beta instead of > starting with 1.03 only to face conversion a month or two down the road? > I am computer savvy and am used to working around beta bugs. Also, I > don't anticipate the need to do any heavy-duty reporting right away. I > just need a place to start storing some data and the beta is a very > attractive-looking place. Any guidance is appreciated. > There is still one major base mechanism that has not seen the light of day. However it is unlikely to affect a new user just entering data. The system design is such that as long as you don't replace any of the base code, e.g. add fields, you will be able to just do a simple import into the new code base. So I think it would be reasonable to start in ebase2 as long as you don't modify the code or expect to redo your mods when the real system ships.
------------------ 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 ---------------------------------------------------------------------
