Hi Dan,
There is a possibility that your DAO library is not properly registered. Do
you know of any other wizards within Access that may not be functioning
properly? With Access closed, click on Start | Run and enter the following
three commands, one at a time:
Regsvr32 Accwiz.dll
Regsvr32 "C:\Program Files\Common Files\system\ado\Msado15.dll"
Regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\Dao360.dll"
Make sure to include the double quotes around the long path names, as
indicated above. These commands will re-register an object library for the
wizard, your ADO object library, and the DAO object library. It will not hurt
anything if you reregister an already properly registered library.
As for splitting, you can always split manually. One advantage to doing so
is that your relationships view will not end up looking like tangled
spagetti. Simply copy the database to a new filename appropriate for your BE
(back-end) database. Then delete all queries, forms, reports, macros, DAPs
and modules from this copy. Delete any tables that you may wish to retain in
the FE (front-end) database as local non-shared tables. Perform a compact and
repair operation.
Now, return to your original database and delete all tables that you intend
to share, leaving any tables that you wish to remain unshared. Compact the
database. Use File | Get External Data | Linked Tables to navigate to your
new BE database. It is best to use a UNC path, so that your table links are
not relying on a mapped drive letter, if you plan on making this a shared
multiuser application. Other tips available here:
Implementing a Successful Multiuser Access/JET Application
http://www.accessmvp.com/TWickerath/articles/multiuser.htm
Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________
