Problems with macro to send object

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I've had the same situation come up several times when I've developed a macro
to send a report (an appointment list in snapshot format) via email. It will
work fine - perhaps for months - and then somehow change from sending a
snapshot format to sending in *.xls format. The *.xls version is gibberish.

To make matters worse, at that point I seem unable to fix the issue, even if
I delete & recreate the macro or delete & recreate the report. The only way
I've found to fix the issue is to actually go back to an earlier version of
the database... and of course that means that I'm having to reenter a bunch
of data manually and may lose data.

I can't figure out the cause of the problem (i.e. what I do to make it
happen) or the fix for the problem.

Please help?
 
Sue,

This is a very strange situation. It sounds like some form of
corruption of your application, although I can't quite imagine what. Do
you regularly compact/repair the database?

If it happens again, the approach I would take is to make a new MDB
file, then import into it all objects *except* the offending macro and
report, compact the new file, compile if it contains any VBA code, and
then rebuild the macro and report in the new file. See if that sorts it.
 
You bet it's strange. Eerie, even.
I'll try you recommendation when it happens again. Unfortunately, it has
happened several times now.
 
Oh - One more thing...
You asked if I regularly repair/compact my database. I have it set to
compact upon closing, so this is done regularly. I think repairing &
compacting both occur when that option is carried out, correct?
 
Correct. I am not sure that it is 100% the same process, but satisfies
me that being uncompacted won't be part of the explanation.

A colleague has suggested that the installation of Access may be faulty,
and suggests to re-install. So far, we can not find another explanation
for the problem.
 
As to the install/reinstall issue...

This has happened both on my home machine & on my work machine at least
once. Would that be consistent with the theory that there was a faulty Access
install?
 
NC_Sue said:
This has happened both on my home machine & on my work machine at least
once. Would that be consistent with the theory that there was a faulty Access
install?
Click to expand...

No. :-(
 
Back
Top