dbTalk Databases Forums  

OutputTo problem

comp.databases.ms-access comp.databases.ms-access


Discuss OutputTo problem in the comp.databases.ms-access forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
bobh
 
Posts: n/a

Default OutputTo problem - 04-26-2010 , 01:50 PM






Hi All,

Has anyone else had this issue............

In AccessXP I use a Docmd.OutputTo a spreadsheet and then I send that
created spreadsheet to a user as an attachment. When the user tries to
open the attachment they get "File Format is not Valid".

I did the process a second time and included me in the email and I can
open the attachment without issue. Any ideas why it does work for me
but not the other user??
bobh.

Reply With Quote
  #2  
Old   
bobh
 
Posts: n/a

Default Re: OutputTo problem - 04-27-2010 , 08:17 AM






On Apr 26, 2:50*pm, bobh <vulca... (AT) yahoo (DOT) com> wrote:
Quote:
Hi All,

Has anyone else had this issue............

In AccessXP I use a *Docmd.OutputTo a spreadsheet and then I send that
created spreadsheet to a user as an attachment. When the user tries to
open the attachment they get "File Format is not Valid".

I did the process a second time and included me in the email and I can
open the attachment without issue. *Any ideas why it does work for me
but not the other user??
bobh.

I'm in deep trouble here and I'm looking for ideas as to what to look
at or reseach to figure out what the issue is as I now have three
users reporting the same problem. Excel by itself works on the users
pc

anyone know if Access 'advanced' wizards need to be installed to use
certain Access functions like OutputTO?
bobh.

Reply With Quote
  #3  
Old   
Salad
 
Posts: n/a

Default Re: OutputTo problem - 04-27-2010 , 09:25 AM



bobh wrote:

Quote:
On Apr 26, 2:50 pm, bobh <vulca... (AT) yahoo (DOT) com> wrote:

Hi All,

Has anyone else had this issue............

In AccessXP I use a Docmd.OutputTo a spreadsheet and then I send that
created spreadsheet to a user as an attachment. When the user tries to
open the attachment they get "File Format is not Valid".

I did the process a second time and included me in the email and I can
open the attachment without issue. Any ideas why it does work for me
but not the other user??
bobh.



I'm in deep trouble here and I'm looking for ideas as to what to look
at or reseach to figure out what the issue is as I now have three
users reporting the same problem. Excel by itself works on the users
pc

anyone know if Access 'advanced' wizards need to be installed to use
certain Access functions like OutputTO?
bobh.

Don't know if this will help
http://support.microsoft.com/?kbid=327764

I looked for "Excel File Format is not Valid" in Google and found the above.

Reply With Quote
  #4  
Old   
bobh
 
Posts: n/a

Default Re: OutputTo problem - 04-28-2010 , 11:48 AM



On Apr 27, 10:25*am, Salad <sa... (AT) oilandvinegar (DOT) com> wrote:
Quote:
bobh wrote:
On Apr 26, 2:50 pm, bobh <vulca... (AT) yahoo (DOT) com> wrote:

Hi All,

Has anyone else had this issue............

In AccessXP I use a *Docmd.OutputTo a spreadsheet and then I send that
created spreadsheet to a user as an attachment. When the user tries to
open the attachment they get "File Format is not Valid".

I did the process a second time and included me in the email and I can
open the attachment without issue. *Any ideas why it does work for me
but not the other user??
bobh.

I'm in deep trouble here and I'm looking for ideas as to what to look
at or reseach to figure out what the issue is as I now have three
users reporting the same problem. Excel by itself works on the users
pc

anyone know if Access 'advanced' wizards need to be installed to use
certain Access functions like OutputTO?
bobh.

Don't know if this will helphttp://support.microsoft.com/?kbid=327764

I looked for "Excel File Format is not Valid" in Google and found the above.- Hide quoted text -

- Show quoted text -

thanks for the link I'll test that but I sure hope it's not a registry
issue as I surely could not get Corp IT to fix each registry on an
enterprise level.
bobh.

Reply With Quote
  #5  
Old   
bobh
 
Posts: n/a

Default Re: OutputTo problem - 04-29-2010 , 03:02 PM



On Apr 27, 10:25*am, Salad <sa... (AT) oilandvinegar (DOT) com> wrote:
Quote:
bobh wrote:
On Apr 26, 2:50 pm, bobh <vulca... (AT) yahoo (DOT) com> wrote:

Hi All,

Has anyone else had this issue............

In AccessXP I use a *Docmd.OutputTo a spreadsheet and then I send that
created spreadsheet to a user as an attachment. When the user tries to
open the attachment they get "File Format is not Valid".

I did the process a second time and included me in the email and I can
open the attachment without issue. *Any ideas why it does work for me
but not the other user??
bobh.

I'm in deep trouble here and I'm looking for ideas as to what to look
at or reseach to figure out what the issue is as I now have three
users reporting the same problem. Excel by itself works on the users
pc

anyone know if Access 'advanced' wizards need to be installed to use
certain Access functions like OutputTO?
bobh.

Don't know if this will helphttp://support.microsoft.com/?kbid=327764

I looked for "Excel File Format is not Valid" in Google and found the above.- Hide quoted text -

- Show quoted text -
Found the issue, for anyone interested the company I work for is
changing email client software, from GroupWise to Outlook2007 which
meant I had to change all my Access applications I have throughout the
company. Each application has some form of email automation in it and
the vba code talked specifically to Groupwise. After about two months
of trying to work vba code to talk to Outlook I found Outlook not to
be very friendly when it comes to email automation from outside
itself. So, I went for a CDO solution which caused many arguments with
Corp IT about openning up a smtp port for email automation out of
Access but it finally got done.
After developing a 'simulated' email form in access, adding the vba
code and testing it I distributed it to all my apps. Two users of a
particular email automation process only have a Subject line, no
TextBody and my code checks each item for data and on the TextBody
item if there is no data I do not pass it along as in,
If Me!bxMess <> "" then
.TextBody = Me!bxMess
end if

This for some reason causes any attachment to get mucked up, after
changing my code to not check the bxMess and just pass the item along
empty or not as in,
.TextBody = Me!bxMess

the attachment is a mighty fine attachment............ strange but
true
bobh.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.