Can"t complete the output operation

Hi
Using Access 2007 and Windows XP
I get the Error : Can't complete the output operation
Error occurs whe I use the sendobject or OutputTo
Ex.
DoCmd.SendObject acReport, stDocName, , Forms!OrderFormMain!DbGeneralEmail
DoCmd.OutputTo acOutputReport, SReport, acFormatHTML, sFile

This error only occurs in the MDE (Access2007) on computers where only the
runtime is installed (tested it on quite a few computers and all are giving
the same error.

On my own computer (full access 2007) I do not get the error. (first there
was an error but after some update - don't know wich one - it disappears
If I use the runtime on my computer like this: "C:\Program Files\Microsoft
Office\Office12\MSACCESS.EXE" /runtime "C:\Program
Files\JAMtech\Smart-ItDemo.mde"
I do not get the error.

This error is bringing my whole project to a standstill.

Help will be greatly appreciated

Thanks Alfred

Re: Can"t complete the output operation

I know this one... Straight from a member of the access 2007 team: "The
OutputTo command is broken in runtime..."

Also, I believe the "SendObject" is broken in runtime as well, as I can't
find many users where this works for them. So e-mailing is basically out the
window for runtime users. One last thing, the Free MS .pdf add-in isn't so
free. You have to have a licensed MS product, and the runtime doesn't count.

They are aware of it, and I sure hope the "OutputTo" is fixed soon, as it's
a show-stopper, IMO.

"Alfred" wrote in message
news:FOWdnTzlhOftJ6fanZ2dnUVZ8tuqnZ2d@saix.net...
> Hi
> Using Access 2007 and Windows XP
> I get the Error : Can't complete the output operation
> Error occurs whe I use the sendobject or OutputTo
> Ex.
> DoCmd.SendObject acReport, stDocName, , Forms!OrderFormMain!DbGeneralEmail
> DoCmd.OutputTo acOutputReport, SReport, acFormatHTML, sFile
>
> This error only occurs in the MDE (Access2007) on computers where only the
> runtime is installed (tested it on quite a few computers and all are
> giving the same error.
>
> On my own computer (full access 2007) I do not get the error. (first there
> was an error but after some update - don't know wich one - it disappears
> If I use the runtime on my computer like this: "C:\Program Files\Microsoft
> Office\Office12\MSACCESS.EXE" /runtime "C:\Program
> Files\JAMtech\Smart-ItDemo.mde"
> I do not get the error.
>
> This error is bringing my whole project to a standstill.
>
> Help will be greatly appreciated
>
> Thanks Alfred
>

Re: Can"t complete the output operation

On Nov 14, 6:31 am, "ARC" wrote:
> I know this one... Straight from a member of the access 2007 team: "The
> OutputTo command is broken in runtime..."
>
> Also, I believe the "SendObject" is broken in runtime as well, as I can't
> find many users where this works for them. So e-mailing is basically out the
> window for runtime users. One last thing, the Free MS .pdf add-in isn't so
> free. You have to have a licensed MS product, and the runtime doesn't count.
>
> They are aware of it, and I sure hope the "OutputTo" is fixed soon, as it's
> a show-stopper, IMO.
>
> "Alfred" wrote in message
>
> news:FOWdnTzlhOftJ6fanZ2dnUVZ8tuqnZ2d@saix.net...
>
>
>
> > Hi
> > Using Access 2007 and Windows XP
> > I get the Error : Can't complete the output operation
> > Error occurs whe I use the sendobject or OutputTo
> > Ex.
> > DoCmd.SendObject acReport, stDocName, , Forms!OrderFormMain!DbGeneralEmail
> > DoCmd.OutputTo acOutputReport, SReport, acFormatHTML, sFile
>
> > This error only occurs in the MDE (Access2007) on computers where only the
> > runtime is installed (tested it on quite a few computers and all are
> > giving the same error.
>
> > On my own computer (full access 2007) I do not get the error. (first there
> > was an error but after some update - don't know wich one - it disappears
> > If I use the runtime on my computer like this: "C:\Program Files\Microsoft
> > Office\Office12\MSACCESS.EXE" /runtime "C:\Program
> > Files\JAMtech\Smart-ItDemo.mde"
> > I do not get the error.
>
> > This error is bringing my whole project to a standstill.
>
> > Help will be greatly appreciated
>
> > Thanks Alfred- Hide quoted text -
>
> - Show quoted text -

Alfred,
if you are not afraid to dig into the code a little bit, try looking
up some examples using the winsock control. It works well for me.
P

Re: Can"t complete the output operation

"ARC" wrote in
news:NED_i.7865$3Z2.7128@nlpi069.nbdc.sbc.com:

> I know this one... Straight from a member of the access 2007 team:
> "The OutputTo command is broken in runtime..."

Could you post a link to this quote, please?

> Also, I believe the "SendObject" is broken in runtime as well, as I
> can't find many users where this works for them. So e-mailing is
> basically out the window for runtime users.

There are many ways to send e-mail with/from an Access application,
including hacking Outlook Express, automating Outlook, and utilizing the
MAPI or CDO libraries. I expect several of them will work in whatever
circumstance.

--
lyle fairfield

Re: Can"t complete the output operation

"Alfred" wrote in
news:FOWdnTzlhOftJ6fanZ2dnUVZ8tuqnZ2d@saix.net:

> I get the Error : Can't complete the output operation

> This error only occurs in the MDE (Access2007) on computers where only
> the runtime is installed (tested it on quite a few computers and all
> are giving the same error.

Access costs what? $120 CAD? If it's just the runtime that fails, then
surely the users will be eager to buy a copy of Access to over come the
problem?

Errors with the OutputTo method returning the message you quote have been
documented here in CDMA since 1998 or earlier.
One replicable cause in Ac 97 (I have never checked in any other version)
is the absence of the database window, or of any form window.

--
lyle fairfield

Re: Can"t complete the output operation

Hi Lyle,

I can't post a quote, as it wasn't from a webpage, it was straight e-mail
correspondence with a member of the access team, which I still have.

Assuming "OutputTo" is broke, how exactly would you get around outputting a
report, with the exception of printing to a driver, such as an external
..pdf?

The upgrade for Access (assuming you own a previous version) is around $110
US. I've thought of one not-so-pretty alternative, for those on the runtime
only, and who do not wish to purchase the full version. Download the access
2007 trial, then run the program directly using full access. The trial gives
90 days of access, I believe, and hopefully they will have put out a service
release for the runtime by then.

Thanks!

Andy

"lyle fairfield" wrote in message
news:mqJ_i.13420$9F1.1698@read1.cgocable.net...
> "ARC" wrote in
> news:NED_i.7865$3Z2.7128@nlpi069.nbdc.sbc.com:
>
>> I know this one... Straight from a member of the access 2007 team:
>> "The OutputTo command is broken in runtime..."
>
> Could you post a link to this quote, please?
>
>> Also, I believe the "SendObject" is broken in runtime as well, as I
>> can't find many users where this works for them. So e-mailing is
>> basically out the window for runtime users.
>
> There are many ways to send e-mail with/from an Access application,
> including hacking Outlook Express, automating Outlook, and utilizing the
> MAPI or CDO libraries. I expect several of them will work in whatever
> circumstance.
>
> --
> lyle fairfield

Re: Can"t complete the output operation

On Nov 14, 5:04 pm, "ARC" wrote:

> Assuming "OutputTo" is broke, how exactly would you get around outputting a
> report, with the exception of printing to a driver, such as an external
> .pdf?

The first thing I would do is to spend an hour or two trying to make
OutputTo work. I'm sure you know that 99.44% of the Access things that
are reported to be broken here in CDMA, are not broken. I would want
to be sure that the broken OutputTo was in the 0.56 %. For my own part
I would put less than 0.56% credence in an unpublished statement, no
matter from whom it came.

If that didn't work I would examine the particulars of the situation
and explore alternative solutions.

If I couldn't find an alternative solution, and assuming this it's
html that is wanted, I'd write my own html creator for the reports and
save the file and e-mail it with CDO. I've done this and it's not that
much of a problem.

And if none of those things worked well, I'd port my reports to an mdb
and hack, if necessary, my runtime creation to include that mdb in the
distribution (and open the mdb reports from the mde).

All of this is the presence or absence of sufficient voltage in a
transistor. We have tools to increase or decrease this voltage. This
means we can do anything.

> lyle fairfield

Re: Can"t complete the output operation

I do have numerous support e-mails from customers backing up this claim,
that they cannnot send quotes via e-mail in the new system, whereas they
could in the 97 version. In fact, if you create a report ribbon menu, and
put on the output to word button, it is enabled in full access, but in
runtime, the button is disabled. This also uses the outputTo command.

That's an interesting thought about generating an html based quote, invoice,
or whatever the output happens to be. I have experience in creating excel
sheets on the fly via an excel template file, however, do you have any tips
on how to do an html version of a quote or invoice?

One other thing, lyle. Have you read the access team blog that talks about
the MS .pdf add-in? It goes on and on about how you can now distribute an ms
..pdf add-in in your runtime apps, and makes it all sound very exciting. They
specifically mention including the .pdf in your runtime. However, the big
gotcha is, you need a paid license of at least one 2007 office product in
order to download and/or use the .pdf add-in. What's up with that? I've
e-mailed bug issues to members on the access team in the past, and always
try to lobby for a truly free pdf add-in, or at the very least, lobby for a
nominal charge to purchase just the add-in (they'd sell very well, I would
bet). Anyway, maybe if enough people make noise on this one... :) Of course,
me being a fool, advertised this to my customers (the fact that .pdf would
now be supported), and little did I know that they would have the validation
& license requirement on the pdf add-in.

Thanks!

Andy
"lyle" wrote in message
news:4107aa68-3991-4737-8b48-8a46fc83fc94@b36g2000hsa.google groups.com...
> On Nov 14, 5:04 pm, "ARC" wrote:
>
>> Assuming "OutputTo" is broke, how exactly would you get around outputting
>> a
>> report, with the exception of printing to a driver, such as an external
>> .pdf?
>
> The first thing I would do is to spend an hour or two trying to make
> OutputTo work. I'm sure you know that 99.44% of the Access things that
> are reported to be broken here in CDMA, are not broken. I would want
> to be sure that the broken OutputTo was in the 0.56 %. For my own part
> I would put less than 0.56% credence in an unpublished statement, no
> matter from whom it came.
>
> If that didn't work I would examine the particulars of the situation
> and explore alternative solutions.
>
> If I couldn't find an alternative solution, and assuming this it's
> html that is wanted, I'd write my own html creator for the reports and
> save the file and e-mail it with CDO. I've done this and it's not that
> much of a problem.
>
> And if none of those things worked well, I'd port my reports to an mdb
> and hack, if necessary, my runtime creation to include that mdb in the
> distribution (and open the mdb reports from the mde).
>
> All of this is the presence or absence of sufficient voltage in a
> transistor. We have tools to increase or decrease this voltage. This
> means we can do anything.
>
>> lyle fairfield
>

Re: Can"t complete the output operation

On Nov 15, 9:17 am, "ARC" wrote:

> One other thing, lyle. Have you read the access team blog that talks about
> the MS .pdf add-in?

It's number 243 on my list of things I must follow-up, right after a
rumour about original 1954 Barbara Feldon bikini shots.