User profiles not workin in Access 2003



I am trying to migrate an application from Access97 to Access2003 and I am
finding that the "user profiles" feature isn't working properly in 2003. We
are following the instructions in the 2003 documentation on how to create a
profile. Basically it is the same as in 97 except that some registry keys
are for HKLM\SOFTWARE\Microsoft\Office\9.0\Access become
HKLM\SOFTWARE\Microsoft\Office\11.0\Access. Basically we create a profile
that is a copy of the Office\11.0\Access key and place it in our own key
(HKLM\SOFTWARE\ourcompany\ourproduct\version\) We then add a RefLibPaths key
for a code library and we also add a Wizards\LoadOnStartup key that has some
read-only ("ro") add-ins we want to load. When we launch the programs
<install root>/msaccess.exe /profile "our profile" ourapp.mdb all we get is
"Microsoft Office Access can't load <install root>..." where install root is
the path to Office 11.

Again, we have lots of experience with this and have used profiles
successfully in Access97 and Access2000. Even if I create a profile exactly
per the instructions in the help and make it an exact copy of the
Office\11.0\Access key it will not run any MDBs. All we get is the
"Microsoft Office Access can't load <install root>...". This leads me to
believe that there is a problem with Access 2003 and profiles or there is a
change that has been omitted in the documentation.

Anyone out there using profiles successfully in 2003 ?

As another note, if I add the RefLibPaths and Wizards\LoadOnStartup info
directly to the Office\11.0\Access key then all works well. This can't be a
solution since I don't want these settings to apply to all uses of access.
That's exactly why I need to and should use a user profile.

Thanks
.



Relevant Pages

  • Re: Bluetooth application development
    ... It's a VERY complex API, maybe the most-complex that I've seen for Windows. ... Why MSDN is not providing enough documentation to develop application from ... I don't see any way to truely automate pairing; ... Here also i have to start the pairing process then Headset profile ...
    (microsoft.public.windowsce.app.development)
  • Re: Bluetooth application development
    ... MSDN does an adequate, barely, job of documenting the API calls and ... Why MSDN is not providing enough documentation to develop application from ... I don't see any way to truely automate pairing; ... Here also i have to start the pairing process then Headset profile ...
    (microsoft.public.windowsce.app.development)
  • Re: Windows Vista and Profile Not Loading (Resolved)
    ... Profile Path Share convention was the issue. ... (which the top level folder - the folder encompassing the user folders ... is not stated in the documentation. ... 2003 Domain Controller to Server 2003 from Native 2000. ...
    (microsoft.public.windows.server.networking)
  • Encoding wmv files using WM ASF Writer filter in DirectShow...
    ... I've read through most of the documentation provided with the Windows Media ... the WME Profile Editor to create a profile that was acceptable to our user. ... The problem is that when I encode at multiple bit rates such as: ...
    (microsoft.public.windowsmedia.sdk)
  • Re: Sysprep on SP2 - Default User profile
    ... There isn't any documentation for the changes to the default user profile ... >in how Sysprep in SP2 handles the default profile? ...
    (microsoft.public.windowsxp.setup_deployment)