[Calendula-devel] data migration
Creede Lambard
creede@penguinsinthenight.com
Fri, 12 Mar 2004 09:42:13 -0800
--tqI+Z3u+9OQ7kwn0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
The problem as I see it is that unless these databases are from programs wi=
th
standardized formats, you are going to have a bunch of tables slapped
together and won't know programmatically which field represents which
information in Calendula's database. I guess you could migrate data to CSV
files and then have a tool to import the CSV information by specifying which
FM/Access field maps to which Calendula field, but I don't think even that =
is
as straightforward as it sounds.
Not to say we shouldn't do it, of course. Just saying it's going to require
some skullsweat before the code gets written.
On Fri, Mar 12, 2004 at 09:08:44AM -0800, Darryl Caldwell wrote:
> Bill, Bill, Bill, where were you when I needed your expertise last year? =
;-)
>=20
> Thanks for that great code snippet. I can see putting that to use REAL
> SOON. The problem to be solved is to start planning for migration of data
> in FM and Access databases over to Calendula. Thomas and others have
> suggested that many small nonprofits use FM and Access to store their
> donor data. Some type of migration tools should be present early on and I
> want to make sure the path is mapped out.
>=20
> -D
--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
* .~. ( : Creede Lambard :
Never rush a miracle man. . / V \ . :------------------------:
You get lousy miracles. /( )\ : creede at :
--------------------------------^^-^^----: penguinsinthenight : =20
Linux. Reliable and free. Pick any two. : dot com :
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--tqI+Z3u+9OQ7kwn0
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD4DBQFAUfZ06RaRqmjNX/0RAiiTAJdr5pvSeGMW9cPx+rkwimXpBktBAJ9CzfZI
AyoOxgIrGsZrZe7R0pttcQ==
=2rNN
-----END PGP SIGNATURE-----
--tqI+Z3u+9OQ7kwn0--