Is it possible to get support from Microsoft for this problem?

[Randy Harris]

I've run into a nasty problem, can't find a way around it.

This line of code:

DoCmd.OutputTo acOutputTable, "GSQ_Criteria", acFormatXLS, FileName

errors with

#2385 - Errors were encountered during the save operation.

The error only occurs on some systems. Other systems (also running XP pro)
get no error at all on that line. Anyone know of another command that can
do the OutputTo? Is there any point in contacting Microsoft? I would be
willing to pay for support if I thought there was a good chance they could
help.

Anyone have a suggestion?

--
Randy Harris
(tech at promail dot com)

[Tom van Stiphout]

On Wed, 16 Mar 2005 23:12:08 GMT, "Randy Harris" <ra***@SpamFree.com>
wrote:

One alternative is to use Automation.
Create an object of type Excel.Application.
Using this object, you can control every aspect of Excel. You can
create a new workbook, poke data into the first sheet, and save it.

The help file for Excel's object model is an optional part of the
Office installer. If you chose the defaults, you may have to go back
and explicitly select it.

If you decide to contact MSFT, be sure to reduce the problem to the
minimum: an Access db with a single table and a single macro with a
single line in it.

-Tom.

I've run into a nasty problem, can't find a way around it.

This line of code:

DoCmd.OutputTo acOutputTable, "GSQ_Criteria", acFormatXLS, FileName

errors with

#2385 - Errors were encountered during the save operation.

The error only occurs on some systems. Other systems (also running XP pro)
get no error at all on that line. Anyone know of another command that can
do the OutputTo? Is there any point in contacting Microsoft? I would be
willing to pay for support if I thought there was a good chance they could
help.

Anyone have a suggestion?

[David W. Fenton]

"Randy Harris" <ra***@SpamFree.com> wrote in
news:c3*****************@newssvr17.news.prodigy.co m:

I've run into a nasty problem, can't find a way around it.

This line of code:

DoCmd.OutputTo acOutputTable, "GSQ_Criteria", acFormatXLS,
FileName

errors with

#2385 - Errors were encountered during the save operation.

The error only occurs on some systems. Other systems (also
running XP pro) get no error at all on that line. Anyone know of
another command that can do the OutputTo? Is there any point in
contacting Microsoft? I would be willing to pay for support if I
thought there was a good chance they could help.

Don't you have to specify the XLS extension?

You also might want to try the TransferSpreadsheet command instead.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Randy Harris]

I neglected to include the previous line, which, (I think) answers the
question.

FileName = CurrentProject.Path & "\GSQ_" & Format(Now, "mmm-dd-yy-hhmm") &
".xls"
DoCmd.OutputTo acOutputTable, "GSQ_Criteria", acFormatXLS, FileName

--
Randy Harris
(tech at promail dot com)
"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@24.168.1 28.74...

"Randy Harris" <ra***@SpamFree.com> wrote in
news:c3*****************@newssvr17.news.prodigy.co m:

I've run into a nasty problem, can't find a way around it.

This line of code:

DoCmd.OutputTo acOutputTable, "GSQ_Criteria", acFormatXLS,
FileName

errors with

#2385 - Errors were encountered during the save operation.

The error only occurs on some systems. Other systems (also
running XP pro) get no error at all on that line. Anyone know of
another command that can do the OutputTo? Is there any point in
contacting Microsoft? I would be willing to pay for support if I
thought there was a good chance they could help.

Don't you have to specify the XLS extension?

You also might want to try the TransferSpreadsheet command instead.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Randy Harris]

I dug into this about a hundred years ago and now I'm having trouble
remembering yesterday. Is creating the Excel.Application object using
early, rather than late, binding? I was advised to change that, which I
did, way back when.

Part of the difficulty with contacting Microsoft, is that none of the
systems that are failing are local. I can't reproduce the problem here.

--
Randy Harris
(tech at promail dot com)
"Tom van Stiphout" <no*************@cox.net> wrote in message
news:lp********************************@4ax.com...

On Wed, 16 Mar 2005 23:12:08 GMT, "Randy Harris" <ra***@SpamFree.com>
wrote:

One alternative is to use Automation.
Create an object of type Excel.Application.
Using this object, you can control every aspect of Excel. You can
create a new workbook, poke data into the first sheet, and save it.

The help file for Excel's object model is an optional part of the
Office installer. If you chose the defaults, you may have to go back
and explicitly select it.

If you decide to contact MSFT, be sure to reduce the problem to the
minimum: an Access db with a single table and a single macro with a
single line in it.

-Tom.

I've run into a nasty problem, can't find a way around it.

This line of code:

DoCmd.OutputTo acOutputTable, "GSQ_Criteria", acFormatXLS, FileName

errors with

#2385 - Errors were encountered during the save operation.

The error only occurs on some systems. Other systems (also running XP pro)get no error at all on that line. Anyone know of another command that cando the OutputTo? Is there any point in contacting Microsoft? I would be
willing to pay for support if I thought there was a good chance they couldhelp.

Anyone have a suggestion?

[Tom van Stiphout]

On Thu, 17 Mar 2005 04:45:37 GMT, "Randy Harris" <ra***@SpamFree.com>
wrote:

If you are sure to have Excel available, use early binding. It also
makes writing the code easier because intellisense will be available.

If not sure Excel is installed, use late binding (Dim objExcel as
Object). I still would develop the code using early binding, and
switch to late binding at the last moment.

-Tom.

I dug into this about a hundred years ago and now I'm having trouble
remembering yesterday. Is creating the Excel.Application object using
early, rather than late, binding? I was advised to change that, which I
did, way back when.

Part of the difficulty with contacting Microsoft, is that none of the
systems that are failing are local. I can't reproduce the problem here.

[Trevor Best]

Randy Harris wrote:

I neglected to include the previous line, which, (I think) answers the
question.

FileName = CurrentProject.Path & "\GSQ_" & Format(Now, "mmm-dd-yy-hhmm") &
".xls"
DoCmd.OutputTo acOutputTable, "GSQ_Criteria", acFormatXLS, FileName

I'd still go with David's suggestion and try out TransferSpreadsheet.

Also, nothing to do with the problem but a handy tip for putting date
stamps into file names is to use international format yyyy-mm-dd, when
sorted alphabetically they are also sorted by date + avoids confusion
between British and US dates.

Date stamps as provided by the OS are anything but reliable, too easy to
change the last modified (edit or in some apps (Access) just open the
file) and the Created date, if the file is a copy is usually later than
the modified date (i.e. it's the date the file was copied, not
originally created), so no followups about sorting by date in exploder
please :-)

--
This sig left intentionally blank

[Randy Harris]

David's suggestion was indeed a good one. I changed the code to
TransferSpreadsheet and it no longer fails. I like your idea for the date
format, I'll be making that change as well.

Thanks to everyone for their input.

--
Randy Harris
(tech at promail dot com)
"Trevor Best" <no****@besty.org.uk> wrote in message
news:42**************@besty.org.uk...

Randy Harris wrote:

I neglected to include the previous line, which, (I think) answers the
question.

FileName = CurrentProject.Path & "\GSQ_" & Format(Now, "mmm-dd-yy-hhmm") & ".xls"
DoCmd.OutputTo acOutputTable, "GSQ_Criteria", acFormatXLS, FileName

I'd still go with David's suggestion and try out TransferSpreadsheet.

Also, nothing to do with the problem but a handy tip for putting date
stamps into file names is to use international format yyyy-mm-dd, when
sorted alphabetically they are also sorted by date + avoids confusion
between British and US dates.

Date stamps as provided by the OS are anything but reliable, too easy to
change the last modified (edit or in some apps (Access) just open the
file) and the Created date, if the file is a copy is usually later than
the modified date (i.e. it's the date the file was copied, not
originally created), so no followups about sorting by date in exploder
please :-)

--
This sig left intentionally blank