Re: Failure of SendObject in Access 2003 Runtime

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

DoCmd.SendObject acSendReport, "BlankReport"
and
DoCmd.OutputTo acOutputReport, "BlankReport", , "C:\RicksOutput"

behave the same; same error message without the option to choose a format
which does appear on the full Access 2003 machine.

"The expression On Click your entered as the event property setting produced
the following error: The formats that enable you to output data ..... are
missing or incoreectly registered in the Windows Registry.

Wonder if a security function might be distrupting output. When loading the
application on the runtime machine the Security Warning pops us stating "The
file may not be safe if it contains code that was intended to harm your
computer."


--
Rick in NS


"Rick Brandt" wrote:

Rick Brandt wrote:
Rick in NS wrote:
Hello Rick:

Well, still at a standstill. I went out a purchased Microsoft
Windows Registry Guide by Jerry Honerycutt and after several hours
of reading and with the info you provided I was finally able to get
the Package Wizard syntax correct. After running Wizard I used
regedit to check all of the keys in Office 11.0 were as you
suggested. Still getting the same error message when attempting to run the
application with Access 2003 runtime.

Do you know if there is a tool available to check to see which
registry entries are being polled when the application runs
successfully on full Access 2003 on the developement machine?

Sorry, I do not.

How about some additional experimenting? If you have just the following in an
app...

DoCmd.SendObject acSendReport, "BlankReport"

Then you should get a popup that allows the user to choose the format for the
attachment. See if that comes up for you and whether you see all of the options
you expect.

Also I would test to see if you have the same problems with the OutputTo
command.


--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com



.

Relevant Pages

  • Re: acFormatSNP Not available for email
    ... > the DoCmd.SendObject method with an output format of acFormatSNP ... > however Access2000 does not recognize the format. ... > Windows registry." ... As you can tell this error message was never updated to include Snapshot ...
    (microsoft.public.access.setupconfig)
  • Re: Year comparison
    ... entering the date in abbreviated format, ... just the line that you provided results in the same error message ... No, YEARreturns 4 digit years, you'd want to use 2005 and 2099, ... but you've altered the validation considerably. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: "file cannot be opened because there are problems with content
    ... You are right to say that customers should not be required to work in XML, and that is one reason why I offer to try to recover documents when I see problems reported. ... The suggestion to save a copy in a different format does offer one way of playing safe, but it requires a lot of discipline, and if you do it, one of the formats must be a non-Word 2007 format - HTML, perhaps, as suggested by your link. ... The error message is a problem is with content - Location:> Part: ...
    (microsoft.public.word.application.errors)
  • Re: Error Message: Cant find Installable ISAM
    ... The database is residing on my machine, ... Error Message = "Couldn't find Installable ISAM" ... Connect property set = Access ... Access 2002/2003 format and tried this as a possibility, ...
    (microsoft.public.vb.database)
  • Re: TypeError
    ... invisible character. ... It took a bit of mucking about to get an example of that error message ... Traceback: ... TypeError: format requires a mapping ...
    (comp.lang.python)