One of the perceived objectives of Microsoft is to tie people into proprietary formats. Why otherwise would it have harassed the ISO and manipulated the acceptance of OOXML of MS Office when ISO had already adopted an XML standard, that of OpenOffice? Despite its representations about inter-operability, MS still intends to tie you into its products. Inn the future, however, open standards will be even more desirable.
Dave Postles
________________________________________
From: Archivists, conservators and records managers. [[log in to unmask]] On Behalf Of Kyle Summers [[log in to unmask]]
Sent: 05 June 2008 15:15
To: [log in to unmask]
Subject: Re: cataloguing using MS Access
Dear Tamsin,
Having been on the 'other side of the fence' I urge you to be careful about
how you structure an Access application for this. Maintaining control over
the structure and quantity of the tables is all-important.
By ensuring the users of this system aren't able to make new tables you will
reduce the risks quite considerably.
Keeping the structure simple will mean that the data migration to your final
system will be simpler, not only for your supplier but also for you when you
check the migration.
If you get it right then you'll begin using your system with a satisfying
head start but get it wrong and you'll be faced with a complex, costly and
time consuming data migration.
Of course, from a supplier and developer perspective that isn't necessarily
a bad thing :)
Kyle
Kyle Summers
Just Breathe
www.JustBreathe.co.uk
|