Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

OutputTo Fails in Run-time

52 views
Skip to first unread message

Bruce McCarthy

unread,
Nov 8, 1999, 3:00:00 AM11/8/99
to
Hi,

I'm a consultant and fairly experienced Access programmer using Access since
1.0.

This problem is with Access 97. When I use the OutputTo method of DoCmd as
follows ...

DoCmd.OutputTo acOutputReport, Screen.ActiveReport.Name, _
acFormatRTF, "Test.rtf", True

... it works fine in full-blown Access, but when I run it w/ the runtime
engine I get the following error:

Run-time error '2281'
The formats that enable you to output data as a Microsoft Excel, rich-text
format, MS-DOS text or HTML file are missing or incorrectly registered in
the Windows Registry.
... for more information about the Registry, click Help.

Clicking help provides some insight that I should be able to make it work.
Also, all KB articles I can find, such as Q173334, imply OutputTo should
work in run-time mode.

The problem is I can't find ANYTHING in the KB or on MSDN that refers to
error 2281 !!

Any help would, of course be greatly appreciated.

Bruce McCarthy
Simplified Systems
541.345.5443 Voice/Fax
bruc...@efn.org

Pratik S. Chipdey

unread,
Nov 8, 1999, 3:00:00 AM11/8/99
to
Hi Bruce,
 
I know this may sound weird, but I have had several experiences with Access where my references have been removed from the project! In your case, however, it is not even a library you are referencing. This could be a security issue (if you are working off of an MDB on another machine) with NT. Here are a few things I would try:
 
  1. Repair and compact the MDB, and try running that.
  2. Compile the MDB and try running that. If you continue to get the error, you may need to reinstall Access.
  3. If you have to reinstall Access, make sure you uninstall it first (thereby eliminating all the faulty wizards)
The funny thing is all of the code is contained in one of the MDE's that ships with Access 97 (Wzlib80.MDE). So it could be a simple matter of re-registering the MDE. But that still doesn't explain why the code works in the full-blown version. Sorry, I wish I had the answer here, but try all of the above steps, and if neither of them work, we'll investigate further.
 
Regards,
Pratik

--
 

Pratik S. Chipdey
Pratik...@Hotmail.Com

Bruce McCarthy

unread,
Nov 10, 1999, 3:00:00 AM11/10/99
to
Thanks for your time on this.
 
Actually I've found that removing the "/profile" from the command line fixes the problem. Now I've got to figure out how to create the profile properly so it can include all the run-time options as well as let me use OutputTo.
Pratik S. Chipdey <pra...@email.msn.com> wrote in message news:eVuHuNkK$GA.177@cpmsnbbsa02...

Bruce McCarthy

unread,
Nov 10, 1999, 3:00:00 AM11/10/99
to
Thanks David. The profile IS the problem. When I remove the profile from the
command line, everything works fine. My problem is what to add to the
profile when running the ODE Tools Setup Wizard. I included the Text and
HTML ISAM and thought that would take care of it (automatically add the
necessary items to the registry). Obviously it doesn't. I've looked, and, at
least on a machine w/ full Access 97, it adds my workgroup file under
Engines\SystemDB and my HelpFile, Icon and TitleBar under Run-Time Options.
I can't find very comprehensive info on this subject.

david <david @ epsom dot com dot au> wrote in message
news:#1pQgF4K$GA....@cppssbbsa02.microsoft.com...


> >... it works fine in full-blown Access, but when I run it w/ the runtime
> >engine I get the following error:
>

> Are you running under a different profile? The reference chain
> starts with the profile name listed under the Access Runtime key.
>
>
> Bruce McCarthy wrote in message ...

@epsomdotcomdotau david

unread,
Nov 11, 1999, 3:00:00 AM11/11/99
to

@epsomdotcomdotau david

unread,
Nov 15, 1999, 3:00:00 AM11/15/99
to
err -- actually we haven't figured this out correctly either.
at the moment I add the ISAM stuff by hand "if it does
not work after installation"

>least on a machine w/ full Access 97, it adds my workgroup file under
>Engines\SystemDB and my HelpFile, Icon and TitleBar under Run-Time Options.
>I can't find very comprehensive info on this subject.

Your profile should be listed under Profiles at
software\microsoft\office\8.0\access\profiles
and/or
software\microsoft\access runtime\8.0\profiles

this should point you to the actual profile, like
software\Practical Treasury Systems Pty Ltd\PTM\4.0

which should have an entry like
...\Jet\3.5\ISAM Formats
which should list the format that you want - like "Text"

you should ALSO have
software\microsoft\jet\3.5\engines
(Which in this case lists the DLLs required for the ISAMs)
and
software\microsoft\jet\3.5\ISAM Formats
(Which is just another copy of the ISAM entries,
which sometimes, but not always, have "Engine" keys that
point to the keys in software\microsoft\jet\3.5\engines)


But I have not yet pinned down what makes these keys
appear - even when doing a full install of Office 97.

David Graham, Practical Treasury Systems
-----------------------------------------------------------

Bruce McCarthy wrote in message ...

>Thanks David. The profile IS the problem. When I remove the profile from
the
>command line, everything works fine. My problem is what to add to the
>profile when running the ODE Tools Setup Wizard. I included the Text and
>HTML ISAM and thought that would take care of it (automatically add the
>necessary items to the registry). Obviously it doesn't. I've looked, and,
at
>least on a machine w/ full Access 97, it adds my workgroup file under
>Engines\SystemDB and my HelpFile, Icon and TitleBar under Run-Time Options.
>I can't find very comprehensive info on this subject.
>
>david <david @ epsom dot com dot au> wrote in message
>news:#1pQgF4K$GA....@cppssbbsa02.microsoft.com...

0 new messages