470,849 Members | 1,230 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,849 developers. It's quick & easy.

"registry error" when exporting Print Preview of a report to .rtf -- /profile

A month ago I posted:
"I built my application with Access 2003 and made a distribution using
the Microsoft Office Access 2003 Developer Extensions.
(I also install Jet 8 as a follow-on action at the end of the
I can install the application on my development PC and on a "bare" PC.
Regardless of the PC where I install, in the installed application (but

not the development version)
File->Export from a Report brings up a dialog box containing "Registry
Error" as the first File Type. Pressing on anyway, and selecting
another type (e.g. .html), then following through with an Export causes

the error dialog: "The formats that enable you to output data as a
Microsoft Excel, right-text format, MS_DOS text, or HTML file are
missing or incorrectly registered in the registry." But it *is*
possible to perform such an export from my development version, on the
very same PC where this message occurs. So it's about what the
*installed* application sees in the registry. Is there some kind of
tweak to the Microsoft Office Access 2003 Developer Extensions ->
Package Wizard
that will allow my installed application to export to .rtf et al?
I finally discovered a way around this. It turns out that the
Microsoft Office Access
2003 Developer Extensions -> Package Wizard creates a distribution
that, during
installation on the user's computer, generates shortcuts containing the
command line option:
/profile {12345-4444... GUID .... }
If the user *deletes* this option from the shortcuts (via right-click,
[Shortcut] Target:...
then she will be able to export print previews to .rtf, etc. without
getting "registry error"
as one of the file types. She also won't get the above dialog.

I went back to the Package Wizard to turn off /profile, but no, it's
not listed! It's
hard-wired! I mucked around in my distribution image (setup.ini,
file.msi, etc.)
but couldn't find any way to "patch" the image to omit /profile. At
the moment I need
to tell my *users* to edit both of the shortcuts after installation!

There could be another fix: add a bunch of key/value/data entries
to the registry under the given /profile {GUID} -- but how do I find
out what keys to
add, and will the package wizard let me create registry keys under the

At least there is a way out, hokey as it is...
Michael Fay

Jun 15 '06 #1
0 2053

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Dave Hammond | last post: by
6 posts views Thread by Don Lancaster | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.