Warning to Access Developers about ACE.
DON'T use multivalued fields (MVF) they are worse than LookUp fields and
SubDatasheets, in fact they (MVFs) are a logical progression in the dumbing
down that started with these abominations.
Having seen and evaluated Access 2007 for a few months now I think this is a
terrible product for developers. If you must use it use Jet 4 or SQL Server
2000 or IBM DB2* as the backend, depending upon your requirements.
However if you are lumbered with fixing a total snafu from a "power-user"
please bear in mind the failure of the Access team to depict the MVF
(laughingly referred to as "complex data") from the ACE database engine in
the Relationships Window as the underlying three table structure that it
really is.
They say this will (as opposed to may) be available in a "future" version of
Access (Access XIII).
Suraj Poozhiyil (Program Manager, Microsoft) has said that the main reasons
for the MVF and the lack of representation of the MVF in the Releationships
window are:
1. for compatibility with SharePoint. (not the most popular product in the
world, to say the least)
2. this release is focussed on power users rather than developers.
3. and they could not give a F--- about developers that insist on using
Jet/ACE (I made that one up, didn't I?)
For those who have not been around the block a couple of times you should
know that both Access 95 and Access 2000 the other two major upgrade
releases were very badly botched. After many SPs to both Access 2000 and Jet
4 they finally got something usable although Access 95 was never any good at
all.
This information is based on Access Beta 2 (Public), although I do not
believe anything has changed in this area in the later builds.