emailing databases to Outlook Web Access

  • Thread starter Thread starter Mark
  • Start date Start date
M

Mark

Apologies for this question being only indirectly related to the focus
of this group, but I'm wondering if anyone has experience sending
zipped Access databases to a Microsoft Outlook Web Access account
(Microsoft® Office Outlook® Web Access for Exchange Server 2003)?

I'm running into a problem where if I send my zipped FE via Outlook
Express it won't show up in my Web Access account. The zipped BE goes
through fine. I use both Outlook Express and Web Access accounts on
the same computer and much prefer sending stuff (especially
attachments) via Outlook Express.

The zipped FE sends and receives fine back and forth between two
regular ISP accounts that I have in Outlook Express. The FE will also
send and be received via Web Access *if* I attach it and send it via
Web Access. I just can't send the same FE from my Outlook Express
account to my (or any other staff person's) Web Access account. Just
the BE.

I think I've narrowed it down to a problem with the FE's reports
collection. I can successfully send the FE via Outlook Express and
receive it through my Web Access account if the FE includes everything
*but* the reports. However, it's evidently not reports, per se -- I
included a couple and it went through, but when I started adding a
bunch more it wouldn't go through. I've got 282 reports in the FE.
It's not an attachment size issue -- sending the database with only
the reports and no tables, queries, forms, macros or modules does not
work. An entirely different database which includes just a few reports
does go through fine.

Anyone have any ideas?
Thanks,
Mark
 
See whether changing the file extension before zipping makes a difference.

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/djsteele
Co-author: "Access 2010 Solutions", published by Wiley
(no e-mails, please!)



Apologies for this question being only indirectly related to the focus
of this group, but I'm wondering if anyone has experience sending
zipped Access databases to a Microsoft Outlook Web Access account
(Microsoft® Office Outlook® Web Access for Exchange Server 2003)?

I'm running into a problem where if I send my zipped FE via Outlook
Express it won't show up in my Web Access account. The zipped BE goes
through fine. I use both Outlook Express and Web Access accounts on
the same computer and much prefer sending stuff (especially
attachments) via Outlook Express.

The zipped FE sends and receives fine back and forth between two
regular ISP accounts that I have in Outlook Express. The FE will also
send and be received via Web Access *if* I attach it and send it via
Web Access. I just can't send the same FE from my Outlook Express
account to my (or any other staff person's) Web Access account. Just
the BE.

I think I've narrowed it down to a problem with the FE's reports
collection. I can successfully send the FE via Outlook Express and
receive it through my Web Access account if the FE includes everything
*but* the reports. However, it's evidently not reports, per se -- I
included a couple and it went through, but when I started adding a
bunch more it wouldn't go through. I've got 282 reports in the FE.
It's not an attachment size issue -- sending the database with only
the reports and no tables, queries, forms, macros or modules does not
work. An entirely different database which includes just a few reports
does go through fine.

Anyone have any ideas?
Thanks,
Mark
 
See whether changing the file extension before zipping makes a difference..

--
Doug Steele, Microsoft Access MVPhttp://www.AccessMVP.com/djsteele
Co-author: "Access 2010 Solutions", published by Wiley
(no e-mails, please!)


Apologies for this question being only indirectly related to the focus
of this group, but I'm wondering if anyone has experience sending
zipped Access databases to a Microsoft Outlook Web Access account
(Microsoft® Office Outlook® Web Access for Exchange Server 2003)?

I'm running into a problem where if I send my zipped FE via Outlook
Express it won't show up in my Web Access account. The zipped BE goes
through fine. I use both Outlook Express and Web Access accounts on
the same computer and much prefer sending stuff (especially
attachments) via Outlook Express.

The zipped FE sends and receives fine back and forth between two
regular ISP accounts that I have in Outlook Express. The FE will also
send and be received via Web Access *if* I attach it and send it via
Web Access. I just can't send the same FE from my Outlook Express
account to my (or any other staff person's) Web Access account. Just
the BE.

I think I've narrowed it down to a problem with the FE's reports
collection. I can successfully send the FE via Outlook Express and
receive it through my Web Access account if the FE includes everything
*but* the reports. However, it's evidently not reports, per se -- I
included a couple and it went through, but when I started adding a
bunch more it wouldn't go through. I've got 282 reports in the FE.
It's not an attachment size issue -- sending the database with only
the reports and no tables, queries, forms, macros or modules does not
work. An entirely different database which includes just a few reports
does go through fine.

Anyone have any ideas?
Thanks,
Mark
Click to expand...

Password protect the zip file before sending it. Usually works fine.
 
Password protect the zip file before sending it. Usually works fine.- Hide quoted text -

- Show quoted text -
Click to expand...

Douglas: Changing the extension didn't help, at least not to ".doc".
All the other .mdb and their .zip conversions go through fine. I've
been trying a number of different variations this morning. I'm in the
process of altering one of the reports piece by piece that prevents
the zipfile from going through.

Jim: Thanks for the suggestion. Unfortunately, our local ISP stopped
allowing password-protected zipfiles a while back.
 
Douglas: Changing the extension didn't help, at least not to ".doc".
All the other .mdb and their .zip conversions go through fine. I've
been trying a number of different variations this morning. I'm in the
process of altering one of the reports piece by piece that prevents
the zipfile from going through.

Jim: Thanks for the suggestion. Unfortunately, our local ISP stopped
allowing password-protected zipfiles a while back.- Hide quoted text -

- Show quoted text -
Click to expand...

It appears I've found the problem. Out of the 282 reports, the first
one that I happened to choose that had code in it (thinking that code
might be the problem) turns out to be the culprit. I could include the
other 281 reports, but omit this particular one and the zipfile would
go through. But it wasn't the code, nor the bound text boxes, nor the
bound memo fields, nor the recordsource -- each of which I tried
deleting in turn. It was one of eight labels in the Page Header. Just
a simple label. After deleting and replacing that label (with the
exact same text and formatting), the zipped database started showing
up in Web Access after sending it from Outlook Express. Prior to
deleting and replacing that label, I had tried Repair, Compact,
importing all objects into a new database, renaming the database --
nothing worked until I replaced that particular label. Good thing it
was the 20th report in the list and not the 282nd! I don't understand
why something like a label could prevent Web Access from accepting a
zipped up database. It seems to be working now, but I wonder about
tomorrow.
Mark
 
It appears I've found the problem. Out of the 282 reports, the first
one that I happened to choose that had code in it (thinking that code
might be the problem) turns out to be the culprit. I could include the
other 281 reports, but omit this particular one and the zipfile would
go through. But it wasn't the code, nor the bound text boxes, nor the
bound memo fields, nor the recordsource -- each of which I tried
deleting in turn. It was one of eight labels in the Page Header. Just
a simple label. After deleting and replacing that label (with the
exact same text and formatting), the zipped database started showing
up in Web Access after sending it from Outlook Express. Prior to
deleting and replacing that label, I had tried Repair, Compact,
importing all objects into a new database, renaming the database --
nothing worked until I replaced that particular label. Good thing it
was the 20th report in the list and not the 282nd! I don't understand
why something like a label could prevent Web Access from accepting a
zipped up database. It seems to be working now, but I wonder about
tomorrow.
Mark- Hide quoted text -

- Show quoted text -
Click to expand...

A little further insight: I created a new database and imported only
that single report -- in the original format. I deleted the problem
label, saved the report, zipped the database and sent it to Web
Access. It did not arrive. I then did a Repair & Compact on that
database, zipped it back up and re-sent it. This time it went through.
Mark
 
Mark said:
It appears I've found the problem. Out of the 282 reports, the first
one that I happened to choose that had code in it (thinking that code
might be the problem) turns out to be the culprit. I could include the
other 281 reports, but omit this particular one and the zipfile would
go through. But it wasn't the code, nor the bound text boxes, nor the
bound memo fields, nor the recordsource -- each of which I tried
deleting in turn. It was one of eight labels in the Page Header. Just
a simple label. After deleting and replacing that label (with the
exact same text and formatting), the zipped database started showing
up in Web Access after sending it from Outlook Express. Prior to
deleting and replacing that label, I had tried Repair, Compact,
importing all objects into a new database, renaming the database --
nothing worked until I replaced that particular label. Good thing it
was the 20th report in the list and not the 282nd! I don't understand
why something like a label could prevent Web Access from accepting a
zipped up database. It seems to be working now, but I wonder about
tomorrow.
Mark
Click to expand...

Wow! What made you think that a label was the cause of the problem and how
long did it take you to figure this out?

Brian
 
Wow! What made you think that a label was the cause of the problem and how
long did it take you to figure this out?

Brian- Hide quoted text -

- Show quoted text -
Click to expand...

Hi Brian,
I just plain stumbled upon the fact that it was that one particular
report. Then, I just started deleting things within that report,
zipping the database up after each change and sending it until it
finally went through. Haven't got much else done today. Just finished
deleting about a zillion trial databases and their associated
zipfiles, and all the junk in both email programs. Beats working my
real job.
Mark
 
A little further insight: I created a new database and imported only
that single report -- in the original format. I deleted the problem
label, saved the report, zipped the database and sent it to Web
Access. It did not arrive. I then did a Repair & Compact on that
database, zipped it back up and re-sent it. This time it went through.
Click to expand...

I suspect the problem was that the file contained what appeared to be
a virus due to string comparisons. And it's your ISPs antivirus
software in the email program which is deleting the attachments/emails
I once was working away on an MDB and suddenly my antivirus program
told me that file had a virus and quarantined it. Real pain it was to
get back into that MDB too.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
 
Back
Top